prendino's comments

It's because they make up a minority whose needs have gone uncared for during their entire working life.

Not everyone is like you. Some just want to go to work and finish their own tickets because the company's culture actively disincentivizes collaboration. Some have ADHD and lose their focus to every little movement in the room. Some are introverts who become much more mentally exhausted from such an environment than their extroverted colleagues. Some have a life besides work that sufficiently fulfills their social needs. Some are utterly disinterested in hearing about Bob's ongoing kitchen renovation or Netflix preferences. Some are employed at a place with poor camaraderie. Some have a position that makes the supposed collaborative benefits of open offices a moot point (work in a distributed team? On a single person project?). But always, they have a people-person manager who thinks everyone should work in-office because water cooler conversations are just so creative and open offices are so dynamic and vibrant. The office is dominated by extroverted people who love these ideas, and they tend to be the ones having their voices heard. Meanwhile, the little man or woman who just wants to work in peace resorts to Hacker News or a personal blog.

And you effectively propose that these people should be filtered out because a few have grown tired of it to such a degree that they misdirect their frustration at colleagues or use toxic language.

The west, especially the US, is so obsessed with diversity but only of the superficial skin color kind. Not diversity of the mind. Imagine if someone had grown cynical and tired of the lack of inclusivity for <insert-race-here> and someone suggested the lack of inclusivity is good because the people with bad attitudes would be filtered out.

Have a good day.

We were taught these things at the Bachelor's program in CS I went to in Sweden. At my first job I then slipped on a banana peel into a de facto tech lead position within a year, and I don't think it was due to my inherent greatness but rather that I was taught software engineering and the other colleagues at my level had not.

Ironically, the software engineering courses were the only ones I disliked while a student. An entire course in design patterns where strict adherence to UML was enforced felt a bit archaic. We had a course in software QA which mostly consisted of learning TDD and the standard tooling in the Java ecosystem, with some cursory walkthroughs of other types of QA like static analysis, fuzzing and performance testing. At the time it felt so boring, I liked to actually build stuff! A couple of years later I joined a team with very competent, CS-educated developers tasked to set up a workflow and all the tooling for testing software with high security requirements. They were dumbfounded when I knew what all the stuff they were tasked to do was!

Never heard of it happening in my lifetime.