Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place.
…really, really suck.
Can you believe I got called by a recruiter who hadn’t even bothered to look at a map to figure out where Rochester is in relation to NYC? She seemed shocked when I said it would be a 6-8 hour drive for me to “commute”. She kept referring to NYC as “the city”, as if none of the other centers of population in New York (or indeed, probably the world) count as cities in her world view.
Feh.
I’ve ranted about the impromptu meetings that break out outside my cube in the past, right? Well, today it reached a new pinnacle of annoying: there were three separate groups talking, and because they were so noisy, each group was getting progressively louder and louder as they struggled to be heard over the other two groups.
After a minute or two of this, I went out and said very loudly “Excuse me, I’m not working too loud for you, am I?” One person laughed, but nobody stopped talking. About two minutes later, two of the groups went away but the one group stayed for another 5 minutes or so.
Next time I’m plugging my iPod into my speakers and blasting “Mao Tse Tung Said” at them.
This office has never been particularly well airconditioned. Mostly it’s too hot in both winter and summer, although a few years ago it was the opposite, so that I kept a sweater in my desk for the days when it was too over airconditioned in the summer. But in the last couple of years, we keep getting “emergency power reduction program in effect”, which means that they’ve turned off at least one of the building’s chillers, usually because one of the (formerly belonging to the company, now sold off to some other organization) power generators is off-line.
Today it’s bloody hot in the office, and of course this is a day when I chose to wear a long sleeve shirt.
One of the trials and tribulations and also one of the fun challenges of my job is that I get vague bug reports on something the QA person sees sometimes and not others. Our QA people don’t do a very good job of tracking exactly what they did and what they did differently between the ones that work and the ones that don’t. Ok, sometimes that’s our fault as developers for not logging enough, but it would be nice if they could tell you, for example, that the one that didn’t work used to be on the schedule before it was removed from the schedule while the one that does work has never appeared on the schedule.
Continue reading “D’oh!”
I swear, the next person I discovered declaring a method as “throws Exception” is going to get a kick in the balls. Serously, what sort of fucked up code are you writing that you can’t even tell what type of exceptions it’s going to throw? It’s head up your ass lazyness, pure and simple. And it poisons the code all up the line because your callers have to do the same, and then their callers, all the way up to whoever is handling the exceptions.