The Bitching Hour Strikes Again



I’ve been there. Could make for an interesting work day. :slight_smile:


What I said:
It’s frustrating when $other_team forwards me messages like “X says the PC is freezing.” Those messages tell me nothing helpful, other than the user’s name. If I emailed them to say, “X says $other_team’s_product is terrible,” they’d be annoyed and need more info.

$Other_team has implied or straight-up told $users that recent issues are $my_software’s fault, then the network’s fault, then the PC’s fault. We test and/or upgrade each item and the $user’s situation doesn’t improve. $Users are frustrated, and I understand why. $Users think $other_team has a base level of IT knowledge. I’ve tried to maintain that illusion, but I won’t lie to them.

What I wanted to say:
$Other_team can barely function with $other_team’s_product, let alone comprehend an error message. They should’ve been given real training on basic troubleshooting a LONG time ago.

We all know that a new software platform for the whole company is coming, and it sure looks like the company is planning to dump $other_team when that happens. I get this. In the meantime, can we at least be straight with $users that we’re just limping along on this old software, and $other_team can’t help them?

No? Because $users are valuable to $company.TF, and might quit or demand more money to stay? Okay, then I would like more money to put up with being the scapegoat for all of the above.


Okay, here is the infamous “thong in the power supply” thread, from June 29, 2004, by Severine, Hands of the Bear:


So yesterday at 17:00 I noticed the DVR guy was examining the cameras we set up for testing purposes outside.

So I stopped and chatted to him. Apparently he was removing one of the cameras as he was going to site the next day and needed it to install on site.

Then he asked me for a network cable. I tole him my PFY is most probably inside and may or may not help him. Then I left for sweet $home (and got caught up in a charlie foxtrot of a traffic jam).

Next day I heard he asked for a network cable but nobody was able to help him. Boo hoo.

Bad planning on his part. Had he informed us that he need to do an install early enough, we would’ve made a plan.


Similar to a poster my mother had at her desk when I was a kid:


I have such a sign up at my desk. :sunglasses:


I think I’ve finally realised that my boss doesn’t seem to know what is going on. There is another developer in our team. His installation of visual studio is fried. So instead of fixing it he’s rdp’ed onto the dev SQL box and installed Vs there. Whatever he’s working on sent the server into meltdown and it needed to be stopped before we could do any work. The last time was the debug process from his program.

Enter bossman.
Me: Server went down Dev processes went haywire.
Boss: maybe we need to look at alternative environments for developing.
Me: told boss that the correct environments for developing code are our own PCs!!! Otherwise this stuff happens!


Hi it’s me your dba.


Your RDP rights to the SQL box just got revoked. If you’re not careful, I’ll revoke your SQL rights too.


Lol! I’ll suggest that to our systems/DBA guys.