Well aren’t they all? Last thing Friday, my colleague who’s training the bits of our new inventory system that I’m not training out myself comes to me with a problem. So I end up doing a database dump and emailing it across to Germany - they don’t have a public holiday so should get chance to look at it Monday. Tuesday - it’s the same old thing; "Works here"\"We think that’s what you asked for". Well they hadn’t actually looked at the problem and then expect me to drop everything and start writing complicated SQL queries so that we can find out what’s wrong. Gah!, that’s why I sent you the bloody dump last Friday so that you could look at it yesterday and tell me what’s wrong with it, not let me sit there and try and work it out for you. Tossers. (And where’s the DBA when you need him?) Anyway it’s a shite system and I’ll be glad when my part in the whole debacle is over (that’ll be when hell freezes over) and either the company survives by some miracle or the whole stinking mess slips slowly into the mire. Then this afternoon, yet again, I’m either expected to drop everything to rewrite a whole bloody report from this system for some wanky developer to check data he’s getting from an add-in system or work several hours into the evening. Well guess who didn’t stay late? (Not more than 15 minutes anyway.) Still it didn’t work and I’m likely to be back in the office at 6.30am trying to trace why!!! Seriously pissed off and perhaps I should have handed my notice in a couple of weeks ago when I felt almost as pissed off as this. I know I should have done it 12 months ago when they ignored my advice and implemented the bloody project anyway. Phew, well that’s off my chest.