I'm not sure it has to do with skill. That would imply the average worker has agency to apply their skills. The dynamic is more: leadership doesn't understand any of technical details and is happy to defer blame on engineers. But engineers are often expressly forbidden from proactively solving problems. So any employee with half a brain can read the writing on the wall - projects will fail due to incompetence (literally no way to stop it) so we might as well prepare to clean up the inevitable mess.
The result: a brittle system that requires heroics just to keep it operating. Once the heroics are rewarded, and proactive problem solving is eliminated, the cycle is locked in place. Cleaning up messes that you yourself begrudgingly create is the new job description.
What is the average tenure in your company? In most tech companies I know, its 2-4 years (add changing teams into that)
A lot of times you are maintaining existing system. Even then you can't blame other engineers, because information/context/constraints they had at that time could be totally different than what you have now.
If business is burning in 2 months, I am willing to create 100K lines of spaghetti code to save it. Afterwards, we can discuss how to rewrite/refactor
Where I work 20 years or so. Many people who switch in never leave, and a lot of kids who started as an intern are now retiring. Some people do of course find new jobs, but it isn't common (and having worked for a lot of other companies previously I'm not looking - we are not perfect but better than many other options). Maybe part of tech's problem is most can't figure out how to keep good people. They throw money, ping pong tables, and the like around. A good stable paycheck where you are expected to work 40 hours a week and go home is worth a lot to many people even if they could make more elsewhere.
> Rewarding only crisis response discourages preventive work and sends the wrong signal about what the organization truly values.