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.
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.
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…
Removed by mod
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.
Removed by mod
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.