Its All About Feedback
summary
Quality gets worse when long feedback latency lets speculation accumulate and QA work disincentivizes developer testing, so the concrete fix is to shorten and clean feedback loops. Examples: a legacy regression drops from six weeks to two weeks with automation, system tests become hours not weeks by removing Gerrit and using pair programming plus direct-to-master commits, and Cloud Foundry teams build a visible pipeline with Concourse CI so merges stop taking four weeks and real feedback returns. Toolsmith teams must be senior and tests require active pruning.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:09Digression: Silicon Valley Circa 1999
- 2:44Digression: STMR 3, Fall 2000
- 5:37Digression: Better Testing, Worse Quality (2001)
- 8:13Examples of Feedback Loops: OODA
- 8:23Examples of Feedback Loops: Lean Startup
- 9:14Feedback Cycle Time Varies
- 12:05Digression: Schrödinger's Cat
- 14:30Digression: Fruit Flies
- 16:00Tightening Feedback Cycles (Example 1) BEFORE: days - weeks Unit Test
- 19:45Tightening Feedback Cycles (Example 2)
- 21:11Polluted Feedback Streams
- 22:27Digression: Word Count Simulation
- 24:54Visibility
- 26:33Feedback Entropy
- 29:07Transformation Lessons Learned
- 34:02Caring for Your Feedback Cycles?
related talks
45mKeynote: On the Care and Feeding of Feedback Cycles
32mOn the Care and Feeding of Feedback Cycles
36mHow programmers & testers can be productive
53mShift Left Testing for Continuous Collaboration
23mA little less testing, a little more quality
10mBeyond “try harder”: Effective strategies to tackle bugs
47mHow to win in software development with tighter feedback loops
57mBlazing Fast Feedback Loops in the Java Universe