|
I polished
DualTimeZone
and made it available on googlecode:
View Sources.
Release installer.
The development cycle was not too bad:
Just a handful of minutes to get the [application's skeleton|ProjectList#appskel] customized for this application.
An hour or so to find the best way to implement the functionality (a timer and 24 icons that get swapped periodically) and another hour to actually implement and check that.
Several hours to polish the application, create an about box, add a French translation and create an installer.
Another hour to blog about this, publish it, create the CVS import, fight with it not showing properly on viewcvs, etc.
Another extra hour to upload it to googlecode.
I'd estimate there was about a 1 to 5 ratio here: 1 hour to implement the real
functionality (it's really low tech) and 5 hours to polish the chrome around it
and deliver, the whole thing split over 3 days. And another day lost trying to
make it available.
Speaking of bloat, the resulting executable is 168 KB, the MSI installer file is 337 KB
and according to the task manager the application uses 12 MB when running yet its VM size is 7 MB.
For comparison, an empty .Net WinForm application (the default WinApp created by the C# wizard in
VS.Net 2k3) generates a 16 KB executable that uses 8 MB of memory and 6 MB of VM when running.
Obviously having a kitchen sink run under the hood has a price in terms of memory usage,
not to mention the hefty 20 MB initial download (which I painfully forgot to load on my
secondary vmware dev box :-( ). |