There was one guy who worked extremely hard and extremely thoughtfully who was a master at low-level and high-level languages. Kind of a John Carmack type. But these people are like unicorns who you meet once in a career.
I've very often had to finalize the famous "last 20%"
of their projects which is a fun place to be in.
"I thought it was almost done?"
In a fair world (or a fair workplace) I wouldn't mind doing that kind of work. Ideally, I'd say "I'm willing to do whatever it takes to ship good code! Hell, I'll mop the floors or go fetch sandwiches if that's what the team needs at that moment!"
But at this point, I really try to avoid it. Unless your manager is attentive and technically savvy enough to recognize the hell you're wading through, it's basically just career suicide. The 10x person gets farther and farther ahead of you. At the end of the month he's got 100 commits and has shipped 5 features and 9 fixes. Meanwhile, you've done some fraction of that.
When I have junior devs tackle a mess like that, I make sure to put extra effort into recognizing the difficult work they are doing in cleaning up somebody else's mess. I make no claims of being a good senior dev or a good manager or anything like that. But I try to do that one thing right at least.
I also worked with another alleged 10x developer. He was quite good, but was also given the bulk of the greenfield work and left a massive trail of technical debt in his wake.
The tech debt absolutely bothers me. It is so destructive to productivity and morale.We had mountains of technical debt in an overstuffed monolith app. Our test suite alone took close to an hour to run and was flaky.
Management was openly hostile and derisive about attempts to address this debt. They were not engineers so it was like a laughing matter to them. "You want to have a portion of the team focus on something other than SHIPPING? Are you mad?"
Idiots. Some of the smartest idiots in the world, but idiots.