> From my experience, it's definitely drifted away from a bunch of nerds solving problems to something more towards emotional/personal/politics. I recently saw someone cry when a person very kindly asked them to explain a discrepancy. "Back in my day" people would just state facts, point out flaws, and argue a bit, and have fun doing it, for better or worse.

In the last few years, I ended up at a bigtech co through an acquisition, and had been someone who was a go-between for solving issues across teams by having a good understanding of everyone else's codebases, tests, build processes, deployment, infrastructure etc. This papered over the culture of siloed development, refusals to think beyond single services etc. I would submit tests and patches, along with tickets describing the bug, impact statement, fix, test coverage, risk, and make myself on-call or directly supervise deployment, etc.

Attempting to continue that in an org x25 larger was met with people firing off angry emails to executives saying their authority was being undermined and made to look bad, when long standing issues were made trivial and fixed by "someone they had never met before", and wherever they came from can they please go back to. I have no idea what a lot of these people were spending so long doing, their commit history was often full of changes that would make you go think "???". I guess it's lucrative to run out the clock year after year on a 180k package, attending meetings where you argue that things are difficult and lets meet again in 3 months? After becoming highly visible for bringing things to attention, I was offered a package to leave, I assume so they could go back to a culture of top down authority and silence.