One of the intended uses of this site is to exchange best practices and learn from the mistakes of other startups. I think that this blog post falls in the seco

One of the intended uses of this site is to exchange best practices and learn from the mistakes of other startups. I think that this blog post falls in the second category. And I don't think that there's anything wrong with me pointing it out. I'm glad it worked out for the folks at Cue, but I think they could have avoided a lot of headaches with some better planning. I'm not suggesting some radical technique I just made up; I'm pointing out that there exist practices that would have prevented a needless scramble. The circumstances of this story should not serve as an example to other startups, but rather a cautionary tale of what can happen to a shop without the proper release cycle and adequate project management in place. My tone may have been a little rough, sure. I probably wouldn't have even commented if the post had addressed what went wrong and what they learned from it. I guess heroic last-minute efforts amount to a more entertaining story than adequate planning, but I think we can all agree on which method is a more reliable way to run a successful software shop.