Arghh! Zombies!

Why won't some things stay down!?

Bringing projects and programs back from the dead is nothing new in the software industry. Which is one of the biggest annoyances compared to some other engineering disciplines. You don't see anyone decide to resurrect a bridge project and go, lets make this bridge longer!

From a business point of view, there is really nothing wrong with extending existing software. For minimal additional expensive, you can get either more revenue, or extend the longevity of it. Nearly all projects have continued development after their initial release. Currently I'm working on a project that had no work done on it. The problems occur when you have a project that was meant to be dead and buried and is now coming back to life. And not in the good Jesus-resurrects-Lazurus sort of way, I'm talking more about a necromancer bringing back a project that is currently brainless and lurching around until someone figures out what to do with it. And our resident necromancer manager has sent it lurching towards me!

This is why I'm complaining. I was 'volunteered' to lead an existing project that was meant to be off shored to the US after its birth and development in Sydney. Unfortunately the person who was meant to take it over resigned. Clearly he saw what was coming and decided to take the window instead of the fire.

As Jeff Atwood would say, in programming, one is the loneliest number. Being the only person in Sydney assigned on this project would suck more than I can describe. Having someone to talk with, and bounce ideas off in real-time is invaluable. There are others who've been on the project before, but pressing on them when they aren't officially assigned to the task would make me feel guilty.

Now where's my shotty?