WordPress Emergency Support — Here We Are!

If you need WordPress tech support in an emergency, if a crises arises and you need your WordPress fixed as soon as you can snap your fingers — here we are!

Well, slightly longer than “snapping your fingers” — but not much.

We pride ourselves not only on our high quality (plus reasonable cost) but, above all, our speed. We’re obsessed. Middle of the night? There. The wee hours before sunrise? We’re there. Some crazy timezone on the other side of the world you’re in? We’re doubly there.

Of course, we can’t promise 24/7 solutions because we’re brutally honest: sometimes, we just can’t solve the problem that quickly. Sometimes, uninstalling this, re-installing that, changing this whole other thing around, just takes time.

Time, and a lot of coffee!

Here’s one tip. Call us any time — but if we don’t answer, it doesn’t mean we’re sleeping. We’re likely focused and it’s 3am here and Miina’s trying to solve this problem, Jesmin another problem, Kristi a third problem — and so we don’t even have the virtual phone turned on! Just leave a message or send us an email. When we come up to breathe soon, we’ll call you back or send you a note.

There’s an obvious question: “don’t you ever sleep?”.

Well, glad you asked! A few things. First, we drink a lot of coffee. Secondly, we do sneak in naps. Third — more seriously (although the coffee point was indeed serious!) — this is an advantage we have to being partially distributed. Although our home base is in Palo Alto, in Silicon Valley, few of us are based on in Tallinn, Estonia — which positions us perfectly so that, at most times, someone is likely focusing.

Conclusion: you need a WordPress fix in a pinch. Well, here we are. Just call. Or email.


How Come WordPress Isn’t More Secure?

A question we get a lot is, Why Isn’t WordPress more secure?

Excellent questions. We used to wonder this ourselves, when we got started!

A few reasons:

First, due to historical legacy reasons. WordPress was built the way it was built, using great technology of the time. PHP was the coolest thing ever! Perhaps today, it is easier to build a safer system from scratch, but it wasn’t when it was first developed. Technologies change, but software remains in the language it was written.

Secondly, there is a trade-off between “flexibility / easy of development” and “security.” Said differently: What makes WordPress so amazing is that it is sooooo easy to work with: you can quickly, trivially, change the source, change a design, add a widget — do almost anything. We love it because, it lets us make any changes we want without much effort. But with great power comes great responsibility: the ease of development has its cost, and that cost is in security (and performance — but that’s a topic for another day). To implement so many ideal security measures would slow down the core dev… and no one wants that. Well, “no one” except for us!

Third, shockingly, many of the security measure are controversial. Incredible to believe, I know! Take, for example, banning IP addresses that hit too many 404‑s. Let me explain. A common tactic to break into a site is to just try lots and lots of URLs, that contain plugins with known vulnerabilities, to see if the user happens to have it or not. If they do — hack! If they don’t — a “file not found” (404) error. But there’s a downside to this: logging every 404, could bloat the database to be huge — thus slowing down the site. Plus, during stages like developing the site, the developers often to to URLs that may not exist — thus accidentally locking themselves out. (No, that’s never happened to me, no, never, and especially not two days ago, which served as the inspiration for this blog post — no, of course not, this is merely hypothetical.) As a result, the core WordPress development team has made a trade-off on purpose: lets leave WordPress with the minimum configurations possible, and then let each site administrator decide for himself which trade-off‑s he/she’s willing to make. As a man who loves flexibility, I support this philosophy.

These are the three core reasons. Perhaps there are more, but it’s too early in the morning for me to think of now!

Any questions? Bueller, Bueller? Just ask!


Client Questions: Where Are Your Developers?

A common question clients and potential clients ask us is, where are your developers?

Excellent question: many people prefer working with people in a similar time-zone, or who speak the same language — or who are next door, so they can go knock on the door and have a coffee (or beat them over the head!).

Answer: the co-founders split between two offices, in Palo Alto and in Tallinn, Estonia. We’re a small team, so when we say “office”, think about 6 people sitting around at table — not the Googleplex. (Yet!). Most of our supporting development team is in Estonia.

Estonia is an interesting and unique place. The birthplace of Skype, it’s also a core European country — but it’s always been a bit on the outskirts. Their language just isn’t related to any other known language (except Finnish and Hungarian, oddly enough) — and the culture is one of Nordic, northern European professionality, seriousness, and problem-solving. 

But the best part of working with Estonians is this: their almost-native command of the English language. The education and entire culture there is, effectively, bilingual in Estonian and English. As a result, the communication is as smooth as our team is professional.

But with the other part of our team in Palo Alto, we have a strong American face as well. Half the team is American, and we understand deeply both the American culture, and the unique dynamics of the tech space and Silicon Valley.

Have any questions? Just ask — we love to talk!