I just happened to get trapped in a 12+ hour development lock-in to finish up on the GIS software my friends and I have been developing. For more than 12 hours we were kept in the dev room, and we were hacking on code we had written a couple of months back. Every aspect of the software was being scrutinized by everybody, and fixes were coded now and then so as to maximize the time that we were there.
We were fed gratituously and I cannot complain about the accomodations. Maybe we should have done this much earlier in the porject, not so that it could've been finished faster, but rather so that we could maximize the budget allowance for the food. And of course the air-conditioned workspace and well lit environment that turns night to day -- giving me the illusion that time stands still and that my body should not rest.
I should really start fixing my biological clock now, because this type of lifestyle isn't making me any more productive. The software, lacking documentation (for the user to see), should be documented ASAP. Here is where I found the value of code documentation and verbose descriptions. Even my fellow developer can now read through the code and figure out what it does and how to use it by just reading through the inline documentation.
And with my bio clock fixed (hopefully ASAP), then I should be more productive with my thesis especially now that I can work closer to home, and with exotic and powerful hardware.
Chilled.
We were fed gratituously and I cannot complain about the accomodations. Maybe we should have done this much earlier in the porject, not so that it could've been finished faster, but rather so that we could maximize the budget allowance for the food. And of course the air-conditioned workspace and well lit environment that turns night to day -- giving me the illusion that time stands still and that my body should not rest.
I should really start fixing my biological clock now, because this type of lifestyle isn't making me any more productive. The software, lacking documentation (for the user to see), should be documented ASAP. Here is where I found the value of code documentation and verbose descriptions. Even my fellow developer can now read through the code and figure out what it does and how to use it by just reading through the inline documentation.
And with my bio clock fixed (hopefully ASAP), then I should be more productive with my thesis especially now that I can work closer to home, and with exotic and powerful hardware.
Chilled.
Comments
Post a Comment