Two Week Code Pushes: Fast or Slow?
I just finished reading a TechCrunch interview with Andrew Anker of Six Apart about their excellent new service, Vox. It’s a nicely conducted interview about a well-designed product that I think will be very successful, but this line struck me as a bit odd:
“Very early on in Voxâ€™s development, we created a two week rapid iteration cycle where we made sure to push code religiously every two weeks. By doing that, we made sure that we were building a design cycle that was always two weeks away from fixing any problem.”
Do bi-weekly code pushes qualify as “rapid” these days? Even at Disney, we generally didn’t take much longer than that, and at Newsvine we push every single day. Multiple times even. We like the rapid pushes so much, in fact, that we even set up a machine to triumphantly speak out the filepath whenever someone pushes out code: click for a sample.
Maybe it’s because I’m impatient about site improvement and problem solving, but Andrew’s statement — if it were applied to me — would advocate a deliberate slowing down of the push cycle (perhaps for the better).
Does anyone else agree? With web technologies the way they are today, do you consider religious code pushes every two weeks a fast thing or a slow thing? Are scheduled infrequent pushes (meaning, much less than once a day) preferable to your development habits?