Tightening the Feedback Loop
summary
Argues that shortening the feedback loop makes developers faster and safer by delivering concrete, timely signals: automated tests plus file-watching auto-runs, editor-integrated failures, and per-commit complexity checks. Demonstrates a working tool, augment, that runs tests, writes JSON metadata, and highlights failures inside Emacs and the shell. Uses mutation testing with Heckle, coverage with rcov, complexity scoring with flog, and simple response-time checks, and shows these reduce unseen side effects and catch regressions earlier.
AI-written summary · about
chapters (5)
related talks
46mTowards Joyful Development
45mKeynote: On the Care and Feeding of Feedback Cycles
33mWorkflow
57mBlazing Fast Feedback Loops in the Java Universe
55mREPLs All The Way Up: A Rubric For Virtuous Feedback Loops
01h 15mTaking Control Of Your Test Environment
35mQuickly and Safely Refactoring Legacy Code
25mHow to do good without doing anything