I'm only 12 years in the industry and that is young compared to some others here but I'll give my perspective.
I would honestly say that all developers outside of companies who activity are going to run out of cash in 6 months have the time and are given the choice.
When management says, we don't have the time the reality is the proposed time given goes beyond a reasonable allocation of time, the max capacity given and or managers bullshit radar amount.
Great developers also are able to factor these tasks into their own ticket time to make the time for the issue.
I've been in countless meetings where individuals will complain about the state of X, how this is a hack, or we should really fix that.
Plenty of times I've seen, "You've got two days of dedicated time to identify, solve and implement."
This is met with various results, individuals taking the time, don't really do any work and consider it free time.
They spend two days just trying to understand even how all the components fit together. Even if you revisit in a month with another two days they'll spend the same two days relearning the same information because they did not retain or make notes to be able to pickup where they left off.
On a rare occasion someone will come in and fix it or move the needle further for the next person. All of these issues tend to funnel into these types of developers and from my sampling they're ~1 per 100 developers at a company.
I would honestly say that all developers outside of companies who activity are going to run out of cash in 6 months have the time and are given the choice.
When management says, we don't have the time the reality is the proposed time given goes beyond a reasonable allocation of time, the max capacity given and or managers bullshit radar amount.
Great developers also are able to factor these tasks into their own ticket time to make the time for the issue.
I've been in countless meetings where individuals will complain about the state of X, how this is a hack, or we should really fix that.
Plenty of times I've seen, "You've got two days of dedicated time to identify, solve and implement."
This is met with various results, individuals taking the time, don't really do any work and consider it free time.
They spend two days just trying to understand even how all the components fit together. Even if you revisit in a month with another two days they'll spend the same two days relearning the same information because they did not retain or make notes to be able to pickup where they left off.
On a rare occasion someone will come in and fix it or move the needle further for the next person. All of these issues tend to funnel into these types of developers and from my sampling they're ~1 per 100 developers at a company.