JTrilogy
The numbers are almost the same when broken up by ideology (conservative/independant/liberal) instead of party affiliation.
It’s not an issue of “crazies on both sides” — mainstream conservative views of recent events are detached from reality. There’s a pipeline of misinformation that starts with white nationalists, runs through InfoWars and their ilk, and eventually leads to OANN and Fox News. Keeping the audience’s attention is the top priority, so facts matter less than feelings.
[1]: https://polsci.umass.edu/toplines-and-crosstabs-december-202... [2]: https://polsci.umass.edu/sites/default/files/Jan6thAnniversa... (page 5)
Given research showing that the most diverse teams are, on average, more successful than less diverse teams [1], should gender or caste or color still never be considered?
People bring more to their workplaces than algorithms and programming languages, their life experiences and worldview can positively influence the whole company.
The employer should encourage new ideas, create an environment where everyone feels empowered to contribute, and facilitate education and improvement for all employees.
Algorithms, programming languages, technology stacks, etc. can all be taught. The perspective an employee brings to the company can not be taught.
I think we would agree that gender, race, and ethnicity are crude proxies for a "unique worldview". There are so many metrics that could be considered: education, location history, age, previous work, hobbies, etc. Even more can be gleaned from a conversation.
A good hiring manager should know that too, and should select candidates who truly complement the team, not just check the boxes for race and gender.
My current reading list:
* Code Complete: A Practical Handbook of Software Construction - Steve McConnell
* Agile Software Development - Robert C. Martin
Upcoming reading list:
* Node.js Design Patterns - Mario Casciaro
* The Pragmatic Programmer: From Journeyman to Master - Andrew Hunt
* Clean Code - Robert C. Martin
* Refactoring: Improving the Design of Existing Code - Martin Fowler
And maybe Working Effectively with Legacy Code by Michael Feathers.
If anyone has any comments or other suggested readings I'd love to hear them!