The real fallacy in the article is an unstated assumption - that developers should be homogeneous. Why not have a "rockstar" Jack and a "sensible" Dianne, in d

The real fallacy in the article is an unstated assumption - that developers should be homogeneous. Why not have a "rockstar" Jack and a "sensible" Dianne, in dynamic tension? Teams of one are the exception. In multi-person teams, focusing on the same attribute not only misses an opportunity to hire developers who complement one another but often leads to outright conflict as multiple developers lay claim to the same decisions or assignments. The author's point is slightly more applicable to choosing a lead developer, where judgment is at even more of a premium and many people would make the mistake of promoting Jack over Dianne because of his higher profile, but even then I think the article does more harm than good.