3 ms·
> "being forced to support, but not allowed to fix" IMO that's a super important point. Having accountability without control is probably the fastest way to bu
by whstl 3y ago
> "being forced to support, but not allowed to fix"
IMO that's a super important point. Having accountability without control is probably the fastest way to burnout and dissatisfaction in my experience. It doesn't matter the amount of hours you put in, it doesn't matter how much vacation you have. It's the difference between a feeling of accomplishment vs the learned helplessness and Sisyphean feeling of endlessly pushing a stone uphill.
And productivity suffers the most. This situation negatively affects the whole system, naturally.
- nine_zeros 3y ago> Having accountability without control My manager: I want this in X days Me: It is unlikely to finish in X days given x,y,z. It is also likely to cause outages. My manager: If it causes outages, we will throw you on a PIP. Me gets burned out. Lesson learned. If a manager forces me ever again, I am going to let the project and the manager fail.
- sam_bristow 3y agoIt sucks when you're in that situation, but sometimes a paper-trail and a dose of failure is the only way people learn.
- nine_zeros 3y agoThe real problem is too much power to management without accountability. If the team suffers due to management decisions, how about we yank the management first?
- whstl 3y agoBut also: There is often zero practical need for rushing things, or for having some complicated vanity feature. This way there is a lot of risk and accountability as far as the team is concerned, but there was nobody up the chain asking for it. The game of Chinese Whispers of features (and deadlines!) is probably the most inefficient part of software development.