Jul 14th 2009 9:24PM There's an underlying assumption here which doesn't hold up. Namely, the assumption that more frequent updates equate to sloppy development practices.
More and more programmers are finding that they can increase quality and decrease risk by making smaller changes more frequently. My own experience programming for financial and scientific applications bears this out. I don't mean to start a debate about software methodology here but simply to challenge the idea that short development cycles are the province of bad programmers. Many of software development's leading lights are moving in the same direction of the WoW team.