Rare Work Whine
I don’t normally talk about work on this blog. But there are some things that require announcement to the world.
1) Product is three weeks behind schedule.
2) Code freeze (no, really, this time.) is tomorrow.
3) It is 5:30 PM at the work site.
4) Email from the designers requesting a major code change.
Ugh. How late is Starbuck’s open again? At least the manager in charge was apologetic.
ob Irony: I have been dealing with a flaw in the design process that caused me to create a part of code on this project in a manner that lacked what I felt was the necessary abstraction for this piece of code. Upon further examination of the code requiring change, had it been built with the proper abstraction in the first place, it would be minimal work to implement the design change. As it is… *sigh* Fortunately I don’t need to change any of the unit tests. (The change removes negative cases, but doesn’t get rid of any positive ones.)
February 28th, 2008 at 19:20
Dude. You totally have my sympathy.
We’re supposed to have a code freeze here too. I don’t see it happening.
February 29th, 2008 at 15:02
Well, I got it done. By 3:30. AM. Ugh. At least I haven’t heard from QA yet. Of course that could be a bad thing…