May 13, 2004

Blogware 1.0

I feel really badly for not saying anything about Blogware going 1.0, but I was kinda waiting for Tom and/or Joe (local folks I know who are doing much of the heavy lifting on the backend) to say something, but it hasn't happened yet.

So here it is: hey ya'll, congratulations!

I'm guessing that they've gotten caught in the typical post 1.0 bug blizzard. What I've seen happen, time and again (after nearly every company), especially for significant releases (the dreaded x.0 syndrome) is that everyone pushes back on 'issues':

  • Oh, we'll defer that.
  • Well, that's not really a bug.
  • Oh, do we have to have that to deploy?
  • ... and so on ...

The day after the "we shipped!" party, while everyone else is off sipping margaritas, hanging out and patting themselves on the back, there is usually a core group of developers who are wondering just what the hell they've gotten themselves into as they break open all the postponed bugs and begin to deal with the wave of issues they've never seen before.

Such is the nature of software development, more so if a dynamic environment is involved (networking, etc.).

Posted by Dave at May 13, 2004 12:09 AM
Comments

You nailed it. Launching "Anything v1.0" is like getting soaked in gasoline and being chased by a bunch of torch-wielding maniacs. Things were pretty stable but the features that were back-burned suddenly become extremely important and need to be done yesterday. And every time we approach a milestone like this I say to myself, "this will be nice... we can finely tone it down a bit for a couple of weeks" and every time I'm terribly wrong. I don't recall for sure but I would guess that I was the kid who put his hand in boiling water 7 or 8 times before I realized just how hot that stuff is. ;-)

Hopefully I'll be able to get my six weeks of family photos up after this week. And maybe even a rant about how the world is against me.

Posted by: Tom McDonald on May 18, 2004 11:18 PM commLink