Spot on. Generalizing: QA/Test and dev people just think differently. I served as QA manager for a while. I was fortunate to have worked with some really, rea

Spot on. Generalizing: QA/Test and dev people just think differently. I served as QA manager for a while. I was fortunate to have worked with some really, really good QA/Test people. They're more rare than good devs. Some individuals can do well in both worlds. I've had great devs who were pretty good at test. It seems to me like these devs came from outside of software and CS. Like from aerospace or ballet or history. I've mentored QA/Test people so they could better automate and manage their work. Then they could pick up tasks like CI/CD, testing scripts, scrub data, etc. But, in my experience, devs are bad at testing, and just terrible at QA. Getting enough QA/Test support on a team in the 90s was a tough sell, even though everyone gave lip service to quality. It's been a long time since I've worked with an actual Test person, dedicated to that role. And that was just 1 person vs 8 devs. So ridiculous. These days, any kind of "test" is done by "business analysts", whatever that means. And I can't recall the last QA person I've worked with (since my stint as QA Manager in the '90s). FWIW, I wholly agree with Dan Luu's observations about today's QA/Test standard practice in software vs hardware.