[malandrew]

You can also be a 25x developer and have net-negative product designers and biz dev people on your team that completely negate or at least greatly attenuate the value you contribute.

Besides people, you also have the value of the solution as well. A top developer creator an overkill solution for a trivial problem doesn't create much value either. The value of a solution is proportional to the cost of the problem.

[malandrew]

gahhhhhhhhh... I hate autocorrect. It results in typos that make you look like a non-native writer in the language and produces more interference in the mind of the reader, not less, because it's easier to read over a simple typo than incorrect diction.

"A top developer creator an overkill solution..." would have read better had whatever typo that had lead to "creator" instead of "creating" had remained in my original text.

At least red underlines instead of autocorrect highlights the error and prompts you to go back and choose the correct word (<-- perfect example... while writing this previous sentence, "word" originally had a typo and was changed to "work")

[taligent]

This is so true. A "top" developer can often be a terrible development lead or software architect. Often because they try and build generic solutions to specific problems.

This is a massive problem in the Java space where you have these design pattern driven designs that are infinitely flexible but ridiculously complex.