Five Things I Can't Stand About Work
Posted: Fri Jan 04, 2008 9:59 pm
This doesn't happen at my current job, as there are only like six of us left and we're all cool. We spend the whole day fingergunning each other and chewing on toothpicks. Here's five things that used to drive me crazy about previous jobs.
The Microsoft Conversation: At some point you're going to get trapped in a conversation where someone tells you what idiots those assholes at Microsoft are. Not that you, your co-workers, or even anyone they've ever spoken to is somehow going to take even a micro-percentage of market share away from them, with any product. This is especially problematic if your company is trying to make something that would be trounced in the marketplace if a company with infinite cash and resources copied it.
The Meeting Not Attended By The Only Real Decision Maker: I used to get these all the time. I thought one of my bosses was a complete cocksucker, so whenever I found myself having to create a meeting about some stupid shit, I'd never invite him. Not that he cared, I'm sure he thought I was a piece of human detritus as well. As a result, all the meetings I held at one of my last jobs were completely toothless and ended with, "Well, this sounds great, but let's ask [Mr. Dickshitter]." There was only a 40% chance that someone would bother to do that and wake the dragon, and it certainly wasn't going to be me. Therefore every moment I spent in a meeting I called was wasted.
The In-Depth Computer Programming Conversation: When I ultimately write the world's best text game at the age of 55 and finally am in complete control of my text-game faculties, I'm definitely going to have a protagonist work in a particular field that he likes just fine, except for when any of his co-workers even remotely attempt to discuss it. To be specific: there is nothing more boring than hearing how someone solved some computer programming task. "Oh," you might think, "you are a piece of crap because I'm sure you think your solutions are so much more interesting, and that you feel you pepper those stories with stuff even non-programmers can enjoy." FUCK no. If anything, mine are worse because I don't get any practice at this. Here's how every one of my software problems gets solved:
- I used a debugger (in Assembly) and realized, "Shit! That wasn't supposed to happen!"
OR!
- I used a print statement (pretty much everywhere else) and realized, "Shit! That wasn't supposed to be there!"
(A big number three, lately, is the, "Why is this doing this? My changes have no effect! Shit, I'm looking at the test server, not the development one! FUUUUCK" It took a while for that one to happen because this is the first job I've had that actually bothered to spring for development and test servers. Look for this one to have a meteoric rise in 2008... er, if meteors rose.)
Oh yeah, one other thing. The whole genius behind "extreme programming" is that it managed to get beyond this, by making two poor saps responsible for some shit. Of course, the downside of "XP" is that people don't want to talk to anyone an hour after lunch, thus creating silent rage when you have to co-program.
"Do You Know How To Get To Barry's Mexican Emporium And FishGrill? No? Let Me Verbally Give You Directions!": This might be a personal thing. I have someone trying to verbally give me directions once a week. I will never, ever, ever remember any of that shit. I have a 50/50 chance of making the right turn off Interstate 25 if I am going home. Also, if I gave a shit, I'd ask you for the final address and get a Google Maps print-out. I don't, so I didn't.
The Team Building Exercise: I had one of these when a bunch of IFers were in town. You know what, it would have been nice to have hung out with J. Robinson Wheeler, Benjamin "Pinback" Parrish, Paul O'Brian, Adam Cadre, Jennifer Earl and Dayna for a little longer, instead of arriving late due to the genius-level command decision of going straight from rafting to a "meal" that was as forced and strained as Jesus and the Disciples holding still for The Last Supper. An ambulance had to be called as one guy practically died due to the temperature changes. Here's a spoiler as to how well the team was built, as a result: everybody hated everybody else, and years later everyone who was still there that wasn't in management got shit-canned. The fucking end.
The Microsoft Conversation: At some point you're going to get trapped in a conversation where someone tells you what idiots those assholes at Microsoft are. Not that you, your co-workers, or even anyone they've ever spoken to is somehow going to take even a micro-percentage of market share away from them, with any product. This is especially problematic if your company is trying to make something that would be trounced in the marketplace if a company with infinite cash and resources copied it.
The Meeting Not Attended By The Only Real Decision Maker: I used to get these all the time. I thought one of my bosses was a complete cocksucker, so whenever I found myself having to create a meeting about some stupid shit, I'd never invite him. Not that he cared, I'm sure he thought I was a piece of human detritus as well. As a result, all the meetings I held at one of my last jobs were completely toothless and ended with, "Well, this sounds great, but let's ask [Mr. Dickshitter]." There was only a 40% chance that someone would bother to do that and wake the dragon, and it certainly wasn't going to be me. Therefore every moment I spent in a meeting I called was wasted.
The In-Depth Computer Programming Conversation: When I ultimately write the world's best text game at the age of 55 and finally am in complete control of my text-game faculties, I'm definitely going to have a protagonist work in a particular field that he likes just fine, except for when any of his co-workers even remotely attempt to discuss it. To be specific: there is nothing more boring than hearing how someone solved some computer programming task. "Oh," you might think, "you are a piece of crap because I'm sure you think your solutions are so much more interesting, and that you feel you pepper those stories with stuff even non-programmers can enjoy." FUCK no. If anything, mine are worse because I don't get any practice at this. Here's how every one of my software problems gets solved:
- I used a debugger (in Assembly) and realized, "Shit! That wasn't supposed to happen!"
OR!
- I used a print statement (pretty much everywhere else) and realized, "Shit! That wasn't supposed to be there!"
(A big number three, lately, is the, "Why is this doing this? My changes have no effect! Shit, I'm looking at the test server, not the development one! FUUUUCK" It took a while for that one to happen because this is the first job I've had that actually bothered to spring for development and test servers. Look for this one to have a meteoric rise in 2008... er, if meteors rose.)
Oh yeah, one other thing. The whole genius behind "extreme programming" is that it managed to get beyond this, by making two poor saps responsible for some shit. Of course, the downside of "XP" is that people don't want to talk to anyone an hour after lunch, thus creating silent rage when you have to co-program.
"Do You Know How To Get To Barry's Mexican Emporium And FishGrill? No? Let Me Verbally Give You Directions!": This might be a personal thing. I have someone trying to verbally give me directions once a week. I will never, ever, ever remember any of that shit. I have a 50/50 chance of making the right turn off Interstate 25 if I am going home. Also, if I gave a shit, I'd ask you for the final address and get a Google Maps print-out. I don't, so I didn't.
The Team Building Exercise: I had one of these when a bunch of IFers were in town. You know what, it would have been nice to have hung out with J. Robinson Wheeler, Benjamin "Pinback" Parrish, Paul O'Brian, Adam Cadre, Jennifer Earl and Dayna for a little longer, instead of arriving late due to the genius-level command decision of going straight from rafting to a "meal" that was as forced and strained as Jesus and the Disciples holding still for The Last Supper. An ambulance had to be called as one guy practically died due to the temperature changes. Here's a spoiler as to how well the team was built, as a result: everybody hated everybody else, and years later everyone who was still there that wasn't in management got shit-canned. The fucking end.