You're viewing a single thread.
When things go right: "WHAT ARE WE PAYING YOU FOR?!?"
When things go wrong: "WHAT ARE WE PAYING YOU FOR?!?"
The secret to a healthy career in IT is to let things break just a little every once in a while. Nothing so bad as to cause serious problems. But just enough to remind people that you exist and their world would come crumbling down without you.
Especially if its a system that you have told management needs to be replaced but they aren't interested in spending the money..
I get really fucking tired of justifying work. Like, I have delivered every single project I've ever been given ahead of schedule. But every time a new project comes up, higher level managers want all these update meetings to check up on the status, discuss risk factors that might prevent it from being delivered, and a bunch of other bullshit. You're the risk factor, motherfucker, you and your meetings. Get the fuck out of my way and I'll deliver it ahead of schedule just like literally every other project I've ever been in charge of. Quit feeling that you need to be involved! You don't. You're a road block that provides no value. Ugh!
Big mood. It is fucking exhausting explaining basic tech concepts to stakeholders over and over.
If you're ignoring all the risk factors, got no contingency plans or measurements against projected time and budget you have delivered everything on time and budget by luck.
If you already have those, those meetings should absolutely be a 30 min weekend meeting to check on status and what else you may need to keep delivering.
I know they should be 30 minutes per week. But they're not, and that's the frustration. A weekend meeting though? I have a feeling that we may perceive work-life balance differently.
Sorry, that was weekly. Weekend can fuck off if you're on schedule.
Acting like the user won't just break things for you, welcome to IT, you must be new.
Where I'm from we call that Laissez-faire IT
And also install Adobe reader.