Work issues

1) A “Principal Development Lead” (aka parallel to my manager) responded to an external team (still within the company) in a very technical and architecture-related email thread with factually inaccurate information. It’s basically been decided that there wouldn’t be anything gained by correcting him, but… Apparently, my lead had already tried to have this conversation with him, but he didn’t believe him. On top of that, it doesn’t help!

2) I need to finish one more bug today; otherwise an additional bug gets tacked on for each of the next two days. Then I’ll be done. Yay for no regressions!

3) A manager brought in chocolate cake today. I can’t have any.

4) My diet is apparently working somewhat. My pants are almost falling off, and I forgot a belt. Abigail thought this was funny.

5) I had actual important stuff to talk about. I forgot it.

Grrr…

“Could you please not reply to *person*? I think the conversation is getting too technical, and I just want to make a few things clear.”
“Okay.” (Insert false happy voice here)

 

It’s a bloody technical implementation issue that will affect other users of the same system! If it’s got a flaw, it should be fixed. Geez.

Admittedly, it’s more important to my team to know WHY things are misbehaving. But… how often do I get to argue with people who actually do technical architecture work? (Answer: As often as I end up talking to them.)

Work Mistake

Well, I’m a complete and utter idiot. The word “Fuck up” (pardon my English expletives) comes to mind.

I screwed up with work last night. I don’t even have a good excuse — I got a bit distracted. It doesn’t help, though.

Probably the worst mistake I’ve made at work. It isn’t insurmountable, I hope, but it is pretty bad.

You see, we’re at review time. One of the good things I’ve done is apparently impressed some people off my team, who I think it would be good for my lead (immediate superior) to talk to prior to reviewing me. There are two big ones who are known by first names (not Bill or Steve, but Ambrose and Lawrence means something on some teams), and then the person in charge of developers on a team we sometimes collaborate with. That developer manager offered me a job, point-blank, at their last meeting I attended — I had jokingly pointed out that his team had no availability for developers at my level (they had one architect level slot available, and I’m not paid nearly well enough to be one of those). He responded by saying that anytime I feel like poking my head up, to let him know — he was certain he could make a place for me.

I figure having my lead talk to him would be a good thing. Except I couldn’t remember his email alias. So I used the autocomplete on Outlook Web Access’s “To” box to find it, as I had the aliases for a few other coworkers.

I then forgot to delete his alias from the To box.

So when I sent a fairly private message to my lead, I also sent it to this other team’s dev manager.

Um. Whoops.