How to finish twice
2007-12-14 Filed in: deployment
Ok, so the Mac project I worked on with Fred was
completed by us on October 1st, as planned.
Except it wasn't. The original specs were so wildly different from the end requirements that we ended up doing a lot more work (mostly paid for). Some major organizational changes as well. Anyway, 10 weeks later, this project is again finished - but this time it's for real, the final DVD image was frozen today.
Many interesting aspects, technically. A Windows + Mac product, of which both GUIs were developed separately, but with a common engine. A pleasant and respectful level of collaboration between the Win and Mac teams, with a willingness to adopt each other's choices, leading to two apps which clearly are native on each yet show a strong resemblance and commonality. One big reason IMO is the use of some strong visual cues, making it obvious that the apps are essentially the same thing (it's all about multi-lingual dictionaries, with a bunch of features aimed at professional translators). All sorts of interesting stuff on the side as well, such as internet-based licensing and automated software updates.
Many lessons also for me in how to carve up an app between developers, how to plan against a strict deadline, how to manage when you're not the manager, how to prepare and push through the final stages, and of course numerous lessons on mistakes to try and avoid next time around.
All in all, a project I'm very pleased with and proud of. Finishing is good.
Speaking of which... it's time to gently but decidedly return to that other project of mine.
Except it wasn't. The original specs were so wildly different from the end requirements that we ended up doing a lot more work (mostly paid for). Some major organizational changes as well. Anyway, 10 weeks later, this project is again finished - but this time it's for real, the final DVD image was frozen today.
Many interesting aspects, technically. A Windows + Mac product, of which both GUIs were developed separately, but with a common engine. A pleasant and respectful level of collaboration between the Win and Mac teams, with a willingness to adopt each other's choices, leading to two apps which clearly are native on each yet show a strong resemblance and commonality. One big reason IMO is the use of some strong visual cues, making it obvious that the apps are essentially the same thing (it's all about multi-lingual dictionaries, with a bunch of features aimed at professional translators). All sorts of interesting stuff on the side as well, such as internet-based licensing and automated software updates.
Many lessons also for me in how to carve up an app between developers, how to plan against a strict deadline, how to manage when you're not the manager, how to prepare and push through the final stages, and of course numerous lessons on mistakes to try and avoid next time around.
All in all, a project I'm very pleased with and proud of. Finishing is good.
Speaking of which... it's time to gently but decidedly return to that other project of mine.