Its ok guys. Few of your of your software bugs are as bad as the ones I get to deal with at my job. I just can't tell you what they are about, or how skull fuckingly serious they are while being casually dismissed by the system architect.
While I know we're not into the same software you guys are, believe me, I know this routine. Customer calls because something they take very seriously isn't working/needs to be different. The devs/system architects tend to handwave their concerns. They may, or may not do it, but rarely do they share either my or the customer's degree of concern about it. So that usually leaves me in the position of pestering people to get stuff done, because only by interrupting their day can I share the need to get it completed with them. Which sucks, because basically every time I have to walk into the developer room I get long-suffering sighs and stares.
My company routinely pushes out same-day fixes, but that's one of the big advantages of developing a web-app I suppose.
So does ours, sometimes. Except we're websites, web apps, database, server, scripting, email, hosting....the whole fucking kittenkaboodle, basically. So of the 1000 problems that we can potentially fix, we have to pick about 4 to 6 a day to action. If it's from one of our biggest customers, it gets done that day if it can be solved. For everyone else.....?
Being tech support is like being the child of divorced parents sometimes. Neither want to talk to each other, and so you become the vehicle for everyone's questions, answers and negative emotions.
Playing GTA 4 on Windows 8. Seriously, it's fucking DRM within DRM within DRM. I'm tempted to pirate it so I don't have to deal with all this bullshit just to play the single-player campaign.
Please log in to Steam.
And please log in to the Rockstar Social Club.
Oh and don't forget to log in to Games for Windows Live!
Blech.