Your username suggests other factors at play...
Re:State of the 10x Programmer in 2018
by KKKKkkkk1 on Sunday February 18, 2018 @09:16PM
(#16410293)
But putting effort into any of those things actually brings productivity metrics down. I don't think that's what our industry means when they say 10x.
Yes, measuring productivity is hard. You can decrease the "productivity" of everyone in a team, yet still end up with a more productive team.
Re:State of the 10x Programmer in 2018
by kenforthewin on Sunday February 18, 2018 @02:45PM
(#16407890)
Yes, 10x is a lot of things. Technical debt is important. But none of that is important if you choose the wrong tools. Why not both?
10x is producing code of such a high quality that time spent in QA doing break/fix dev is negligible.
10x is thinking up front about the data model and technical design before writing any code.
10x is maximizing simplicity (no unnecessary abstractions, etc.)
10x is having a deep understanding of the environment (OS, language, supporting libraries, etc.)
The difference between 1x and 10x is decreased time spent downstream in the development process, reworking code that doesn't work, maintaining it after, etc.