David Szetela from Search Engine Watch posted an open letter to Google Engineering asking them to please slow down a little. The basic assertion is that Google Engineers are moving so quickly that they are not taking the time to thoroughly test new code. And as a result, bugs are making it into live code. His proposed solution is to slow down and test more rigorously.
But here's the thing, Google: you're already waaaay out ahead – for example, your Google AdWords campaign management software is two generations or more ahead of Yahoo and Microsoft. So you can afford to slow down a bit and test more rigorously before even minor software releases. You're starting to get a reputation for developing buggy software – one that's not deserved for the most part – and now is the time to nip the problem in the bud before the perception starts to snowball.
While I agree with the goal of producing code with fewer bugs, I think the proposed solution is misguided. Google has successfully created a culture of velocity and execution that has been tremendously successful. Slowing down would be a significant mistake. In a recent New York Times interview Google's CEO talked about velocity,
VELOCITY does, indeed, matter, and Google deploys it to great effect. Conventional software is typically built, tested and shipped in two- or three-year product cycles. Inside Google, Mr. Schmidt says, there are no two-year plans. Its product road maps look ahead only four or five months at most. And, Mr. Schmidt says, the only plans “anybody believes in go through the end of this quarter.”
Speed is a key advantage, and not something that should be sacrificed lightly. If Google is in fact way ahead of Yahoo and Microsoft, and I believe they are, then more power to them. In fact I hope they keep screaming along. I'd rather see Microsoft and Yahoo fall so far behind that they have no choice but scrap their old models and reinvent themselves into leaner, faster companies. Besides, slowing down doesn't guarantee better quality. We can point to endless examples of slowly developed buggy code from Microsoft.
A better challenge to Google engineering would be to create a testing process that can keep up with their current velocity. If they've been able to reinvent application developement, why not testing as well?
