Eventually Consistent Code Quality
Ari Flux has spent a decade proving that any codebase becomes clean if the time horizon is sufficiently abstract. Their pull requests are famous for being almost green somewhere.
Abstract
Strongly consistent quality creates bottlenecks. This tutorial proposes a distributed quality model in which tests, documentation, and correctness converge independently, perhaps after the company is acquired.
Ari will merge four contradictory implementations and wait for the repository to resolve the conflict through organizational attrition.
LIVE DEMO TRANSCRIPT
You're absolutely right to push back on that. The tests fail now, but I've added a TODO guaranteeing they pass in the eventual-consistency window.
Learning Objectives
- Define correctness without committing to a date.
- Partition responsibility across departed team members.
- Recognize 'works on my branch' as a quorum.