Dammit, Jim, I'm a programmer, not a...

...manager. 'Cept I seem to be. Bother.

N. called me this morning for an update on whether P. had fixed a bug. Wha? He wasn't assigned to fix that bug, he was assigned to do several other things. But he found the bug, so surely he should fix it, someone has to fix it....

Yeah, someone does. And maybe it will be him. And if you'd told me that bug was bothering you, maybe I'd have kicked it up the priority levels. But I assigned him to something else, because (a) I didn't know the bug was still present and (b) if I had I wouldn't have assigned him, because I was being told that the something else was super-critical, whereas this bug didn't seem to be (doesn't affect any current clients, could be fixed after initial demo to new clients).

Somehow this translates to not keeping track of my team members well enough in her opinion. And maybe she's right. But I don't want to be a manager, ESPECIALLY not while also trying to be a programmer. I could pretty much lose my mind here.

Did I mention the whole fucking "find the bug" thing occurred during my vacation last month? And generated only a SINGLE email to me, which noted the conditions under which the bug did and did not occur, on Monday of the second week of my vacation?

I just want to design and write things, and make them work. Gah.

Wow, and he's musical, too.

From an email sent out to the company, announcing someone moving into a recently-vacant position (vacant due to the person who occupied it moving away from the office where it had to be done).

[Name] attended [University] as a Business Economics major and is currently rapping-up his courses at a local college.

Normally, when I take courses, I just try to complete them...I hope his professors share his taste in music.

Okay, so I shouldn't be laughing at typos, but I thought that one was cute.