3 ms·
Not all 10x programmers are created equal. Some of them leave a disaster in their wake. They're fast because they're sloppy, and don't take the time to refacto
by Teckla 11y ago
Not all 10x programmers are created equal.
Some of them leave a disaster in their wake. They're fast because they're sloppy, and don't take the time to refactor their new code into something maintainable. The team pays the price for that later.
I'm not suggesting John Carmack is one of those bad 10x developers, but they do exist. Just something to keep in mind.
- dmix 11y agoSuch 10x programmers are perfect for some situations, for example building a prototype. It may be wise to leave it as a prototype and build V2 from scratch after that point - taking many of the best parts from the earlier experiment. I've been on the former end enough times where I'd rather the next team of engineers didn't use it as the base. I often learn many lessons from building V1 which would be a strong base for rebuilding it properly. Erlang creator Mike Williams: “If you don’t make experiments before starting a project, then your whole project will be an experiment”. Unfortunately many startup founders don't see the dev process as experiment-driven, rather as a monolithic beast the continually needs evolution and refinement. The opportunity costs of rebuilding a prototype-quality app using lessons learned from it vs building on top of it are real - rebuilding is not always as risky as many people make it out to be. Context matters.