The real question is why does the top 3 problems on the list appear?
1. Being stuck in problem solving
2. Time pressure
3. Bad code quality and coding practice
You won`t be stuck (often) in problem solving if you have good management and "no question is dumb" atmosphere in the team.
You won`t have (often) time pressure if the project is managed correctly.
You won`t have bad code quality if the management choose to pay for several very good devs/architects and did not impose constant time pressure.
Etc, etc.
My number one reason to losing motivation on work (and subsequently quitting if that does not improve) is a lack of good leadership. I can sustain anything else (if it is not constant) if managers are true leaders. Sadly, they are in a very small minority from my experience so far :(
Because good management understands the value in avoiding getting stuck in problem-solving mode.
It's not that management solves the problems. It's that you structure processes such that they arise far less often, and can be resolved far more readily.
I understood their point to be that good managers allow _adequate time_ to solve problems in a way that decreases unnecessary stress and technical debt.
1. Being stuck in problem solving 2. Time pressure 3. Bad code quality and coding practice
You won`t be stuck (often) in problem solving if you have good management and "no question is dumb" atmosphere in the team. You won`t have (often) time pressure if the project is managed correctly. You won`t have bad code quality if the management choose to pay for several very good devs/architects and did not impose constant time pressure. Etc, etc.
My number one reason to losing motivation on work (and subsequently quitting if that does not improve) is a lack of good leadership. I can sustain anything else (if it is not constant) if managers are true leaders. Sadly, they are in a very small minority from my experience so far :(