Ridiculous emotionally-driven opinionated politicized tribalism is already all over the place in software development. Compared to the other engineering discipl

Ridiculous emotionally-driven opinionated politicized tribalism is already all over the place in software development. Compared to the other engineering disciplines, programming doesn't even fit this title most of the time. What he describes doesn't introduces anything new to current behaviours, American Politics are already everywhere. While it's a gross overestimation to place whole languages in buckets just like that, it doesn't mean things have to fall in one bucket only. For the Mars Rover, you want mission critical batshit conservative programming practices. The JPL coding standards do the job perfectly for that. On the other end of the spectrum, you've got Joe's webpage. I completely agree with you about the bad image of american politics and the incomplete one dimensional line view. However, I do believe software development practices can be classified, it just needs to be in a tree or a graph instead. In order to stop the current meaningless fights over using/doing something or not, lines have to be drawn somewhere. People don't know what these lines are and the industry is plagued with projects having to live with the wrong decisions. He clearly mentions it's not like american politics and I agree on that. It can be useful to actually educate the industry on what exists so they use the right tool for the right job, which currently only rarely happens. It doesn't encourage "good enough" practices, it promotes knowing when to use what. He got the idea right, he only omitted to mention that these line can split multiple dimensions.