3 ms·
The thing about this is its repetitive and useless, constantly draining of brain power. In my job, I respond to emailed/ticket incidents. I do the work to fix t
by PenguinCoder 4y ago
The thing about this is its repetitive and useless, constantly draining of brain power. In my job, I respond to emailed/ticket incidents. I do the work to fix the problem. I note the work and fix in the ticket.y manager wants a weekly report on "what you accomplished this week". Then we have a weekly stand-up meeting with the whole team. And THEN I have 1on1 meetings to discuss what I'm working on.
At this point, I've done the work, documented a fix, written about the problem and the fix in three different places, and then talked in two meetings about the problems and the fix. Why the shit do I have to relive this problem 5 times just to make a manager happy with "staying in sync". I spend more time TALKING about the problem than it took to fix usually. The only thing I should need to tell my manager is when I can't meet the deadline and WHY. Not explaining and repeating my work 5 times.
It's beyond inefficient, it's not a matter of allocating resources, it's an asinine waste of time.