CocoaDust

That last post was a tangent from my original thought bubble of when we were likely to get a ship date for Leopard and the futility of planning for future versions of Mac OS X.

It matters to me because I need to know what’s coming and plan for it. I have a fair idea of what I am doing for the rest of the year; what makes things difficult is the way software sales nosedive during the summer months.

Timing is everything. I need to get major releases out during peak periods, no good releasing software if everyone is up a mountain or at the beach. If Leopard is going to be out in June, just before sales start to dip (I think Leopard can get away with such seasonal trends) then great, I can do my best to get updates out before then.

However, if it’s going to be around April or early May and I need to do Leopard-specific work (because we just don’t know) then my current plans would need some adjustment, because there are plenty of other things I could be doing too.

Of course, if Apple thought a lot of work would be required, they’d let us know about it sooner, but I work up to the wire. It is so easy for my time to be devoured by events in ways that simply allow me to maintain the status quo. This year I am really determined to go beyond that.