I really don't like the concept of a 10X developer - it implies linear scaling.
If you keep writing very similar implementations of very similar things (without actively damaging the code-base) you may very well be an O(n) developer. You keep working at the same pace regardless.
If you are a developer of some calibar, the work that you've already done will feed back into the work that you're doing - making you an O(log(n)) developer, until the work levels out and you slip back toward o(n).
Then there's the other end of the stick, the idiot who has no business writing code, but who management keeps around because he's cheap in the short term.
Everything he touches turn to shit, each change corrupts the code base just a little more, and each change to the corrupted code takes an amount of time proportional to the level of corruption.
This is the O(k^n) developer, and he needs to be stopped.
How do I know if I am an O(k^n) developer? My first "software engineer" job I did absolutely nothing but write update scripts, incredibly minute fixes to 10k+ line stored procedures and then helped watch deployments. I left that one for a new one, and I feel very slow compared to my coworker and I know that most of the time my designs for new features are extremely lacking. Should I leave my position since I fear I am impacting his ability to have high quality code?
In my experience the worst developers never ask if if they are doing things wrong and what that might be.
Look at the chages you're making to the code - are they of a quality comparable to what was already there, do they integrate cleanly, are you coding with a style that fits in with the surrounding code?
If not, what could you be doing better and why aren't you already doing it?
It may take longer in the short term, but give consideration to your development practices. Eventually you'll find yourself more quickly writing a higher quality of code that's more maintainable with fewer defects.
If you keep writing very similar implementations of very similar things (without actively damaging the code-base) you may very well be an O(n) developer. You keep working at the same pace regardless.
If you are a developer of some calibar, the work that you've already done will feed back into the work that you're doing - making you an O(log(n)) developer, until the work levels out and you slip back toward o(n).
Then there's the other end of the stick, the idiot who has no business writing code, but who management keeps around because he's cheap in the short term. Everything he touches turn to shit, each change corrupts the code base just a little more, and each change to the corrupted code takes an amount of time proportional to the level of corruption. This is the O(k^n) developer, and he needs to be stopped.