I love the first graph on Jeff's article. It shows how versatile the "best"-word can be in such a context:
- If you have the best programmers in the world but they failed to help you identify when/where to pivot, you fail.
- If you have the best programmers in the world but let them run too fast and burn, you fail.
- If you have the best programmers in the world but let their ego/drive ignore customer feedback, you fail.
- ...
There is no definition for "the best" beside a "well balanced human being"...
I have been researching this exact space for the past few months (www.developersjourney.info) and am now more and more convinced that once you reach a technical-threshold, in order to close onto "better-developers", you need to hunt for the 3-C-values: create, care and criticize. A balanced team should be a patchwork of cultures, backgrounds, desires and skills. But I think the drive toward those 3-Cs isn't optional...
Plug: This is very much an ongoing thoughts-process for me. If you have further input for my DevJourney Project and/or want to appear on my podcast on this subject, please contact me!
There is no definition for "the best" beside a "well balanced human being"...
I have been researching this exact space for the past few months (www.developersjourney.info) and am now more and more convinced that once you reach a technical-threshold, in order to close onto "better-developers", you need to hunt for the 3-C-values: create, care and criticize. A balanced team should be a patchwork of cultures, backgrounds, desires and skills. But I think the drive toward those 3-Cs isn't optional...
Plug: This is very much an ongoing thoughts-process for me. If you have further input for my DevJourney Project and/or want to appear on my podcast on this subject, please contact me!