He's not promoting that removing dedicated testers is a good idea. Full(er) quote: > Several strategies are getting deployed — shift left (e.g., more unit te

He's not promoting that removing dedicated testers is a good idea. Full(er) quote: > Several strategies are getting deployed — shift left (e.g., more unit tests), shift right (e.g., test in production), transitioning from manual to automated testing and even removing distinct tester roles and trying to hold developers accountable for the quality of the code they are writing. > > These testing strategies are met with varying degrees of success and can even differ from team to team based on skill level, maturity, and culture. By all means, have developers write their own unit tests. To show their intent, document use cases, etc. And do not leave that to a junior colleague or a brain dead AI, optimizing for high McCabe complexity code coverage or whatever metric. AND (indeed) have QA done by someone with different skills. Development requires a focused mindset, in the zone for long stretches, int the box. Test requires distraction, exploring, out of the box — "hey, that's weird" or "I wonder what will happen if I do this".