The author plays to the stereotype of developers who recklessly "commit and forget it". In a properly run organization, QA takes note of developers who consiste

The author plays to the stereotype of developers who recklessly "commit and forget it". In a properly run organization, QA takes note of developers who consistently commit show-stopper bugs. If the QA team is positioned as a clean up crew for shabby code, this is a failing of the organization rather than the developers. In an organization in which tests are developed for any code committed, and developers are careful not to break a build, soft issues are still caught by the QA team. Things that work but not as expected, minor cross-platform glitches, and permutations you'd never think to check, are all commonplace catches for a professional QA tech working with a well functioning development team. The author of the article really doesn't sound like he's worked with a decent dev or QA team.