Meanwhile, today was supposed to be the final release candidate for our software. We failed to meet the deadline. We might be able to meet next week's deadline; it depends on many things. My bug list is down to around ten. I was here until 10.30 or so last night trying to fix one of them, a complex nasty problem that requires I rearrange the order of messages $PRINTER is giving me before I pass them on to $STATUS_REPORTER, something I should probably have known two months ago. The concept was simple, the fix was easy, but a minor niggling detail I missed caused me to spend four hours wondering why I kept locking the debugger.
Well, that and Visual Studio being a piece of crap. How do people use it?
In other news .... Monday I got my annual performance review.
I was terrified. I mean, I started this job trying to do the job of two people, on a new code base with nonexistent training. I got overwhelmed. I failed utterly and they split the job into two jobs (the right move) about the time we missed our alpha date. Since then my stuff has been more or less under control, but the project is still behind schedule. Way behind schedule. Barely staying afloat, in fact. At the end of the day it's my fault for not seeing that i was overwhelmed sooner, and/or not digging myself out from it. And, despite the fact that I shouldn't care overmuch, seeing as I'm busy on the law school quest, I do care.
My review was generally good; in most areas I exceed expectations, according to the HR-approved worksheet, and in every area I at least meet them.
So what are the expectations? And why are my expectations so wildly out of line with reality?
| < Dell and Linux | BBC White season: 'Rivers of Blood' > |
