Developers vs Quality Assurance
summary
Idea starts over a beer and documents a hard lesson: mismatched expectations cost time and morale, not character. Claims that one-line commits often trigger full regression work so one line change causes half a day of testing, that many tests remain manual and boring, and that finger-pointing wastes energy. Recommends concrete fixes: share technologies and pair work, frequent desk-to-desk syncs, and stop treating roles as hierarchies so collaboration actually speeds safe deploys.
AI-written summary · about
chapters (12)
- 0:00Introduction to collaboration
- 1:26Beer-fueled problem discovery
- 2:09Different perspectives QA vs developers
- 4:19Developer-QA conflicts explained
- 7:33Public service announcement on testing
- 8:44Superhero developers and salary-focused ones
- 11:14Finger pointing and shared responsibility
- 13:17Consequences of poor collaboration
- 14:05Key points for better teamwork
- 15:52Discussing professionally vs personally
- 17:16Michael Jordan quote on teamwork
- 18:26Q&A on communication importance
related talks
36mWhole team quality: In the same boat or up the creek?
35mWhy Software Engineers Should Make Quality a Priority
43mBuild in Quality
14mThinking of Quality as developer productivity tool
15mHow to NOT waste time
17mMake Work Not Suck Improving the Developer Experience
38mBuilding a high quality product
28mHow to prioritize dev experience in the development process