This doesn’t happen when developers have trust they’ll be allowed to refactor although sometimes it’s a case of learned behavior from previous employment.
To my surprise, this is not always true. Some engineers do things because they have fun, even senior ones, and they will keep on refactoring things until there is a hard stop.
Best is to never generalize. It may depend from team to team, etc.
Having said that, I am very skeptical about what some people identify as tech debt. Things like "we're using X logger instead of Y logger, this codebase is unmaintable" I tend to not prioritize, but things like "this system looks weird and we don't understand if the code is wrong or the documentation is wrong" is something that should be addressed with high urgency. It's very easy to spend a lot of time maintaining misbehavior that should just be fixed, and the first step is understanding whether or not something is wrong.
But anything longer gets thrown to backlog
Fwiw. I've been a hands on techie for 20 years, then ops manager for 5. I've certainly been an Inexperienced/been a bad manager at times (especially as for a while, highly functional specialized vols reported to me as well), and I'd like think I'm becoming a decent or even good manager. But even still, there are definitely teams and individuals that I will feel the need to manage and focus ; vs others that I feel I can let prioritize and self manage.
(In the ops, of course, establishing formal urgency levels and resulting comms expectations and paths, can reduce stress on EVERYbody)
Employees who can prioritize well will naturally be given more independence to make choices than those who don’t.
This of course assumes the management is able to make good decisions about prioritizing but I think the commenter should be given benefit of the doubt here.