Usage is like oxygen for ideas. You can never fully anticipate how an audience is going to react to something youâ€˜ve created until itâ€™s out there. That means every moment youâ€™re working on something without it being in the public itâ€˜s actually dying, deprived of the oxygen of the real world.
On WordPress.com we deploy code to production twenty or thirty times a day and anyone in the company can do it. We measure the deploy time to hundreds of servers and if it gets too slow (more than 30-60 seconds) we figure out a new way to optimize it. In that short rapid iteration environment the most important thing isnâ€˜t necessarily how perfect code is when you send it out, but how quickly you can revert if you need to so the cost of a mistake is really low, under a minute of brokenness. Someone can go from idea to working code to production and more importantly real users in just a few minutes and I canâ€™t imagine any better form of testing.
Awesome. Thanks for the heads up Ryan.
While we have been able to to a scripted update to our entire server farm in less than sixty seconds on T4, we aren’t quite there yet on T5. We must improve our efficiencies on our newest technology, and we are working on that.