6 ms·
10x is having the experience and ability to accurately provide a 20/80 (or some range) estimate. 10x is producing code of such a high quality that time spent i
by TYPE_FASTER 9y ago
10x is having the experience and ability to accurately provide a 20/80 (or some range) estimate.
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.
- OnlyRepliesToBS 9y ago10x the pay, right? RIGHT? crickets
- kenforthewin 9y agoYes, 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?
- jxub 9y agoYour username suggests other factors at play...
- deleted 9y ago[deleted]
- KKKKkkkk1 9y agoBut 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.
- nkuttler 9y agoYes, measuring productivity is hard. You can decrease the "productivity" of everyone in a team, yet still end up with a more productive team.