finding things that could be better or tools that should exist but don’t, and that if materialized would solve multiple problems at once instead of just one; and
explaining why that’s important in a way that everyone can buy into and dealing with naysayers who’ll want to cut you down and doomers who will say it’ll never work; and
have the focus, discipline and grit to make it through a 10k LoC project and land it on the other side while ekeing out code review along the way and not tripping over loose cables and uneven steps of your initial design / architecture / model that was either flawed from the outset or not malleable enough to fix after a month of entrenchment into your code; and finally
once you’re ready, to then go over the entire codebase and lift the old code up into your new way of doing things so that there is no split brain between the old way and your new tool:
then you can make it as a 10x engineer. It is exhausting but so is running up and down a football field, cycling laps around France, or serving tennis balls at 90mph for three hours at a time. Taking the elite-coder staff-engineering path isn’t for the faint hearted.