Patterns Worth Stealing
Seven volumes describe one system about one dance. None of the ideas in them are about dancing. Here they are again as five scenes you can take to any problem, each with the failure it prevents and the place it earned its keep.
- volumes behind these
- 8volumes behind these
- patterns
- 19patterns
- of them about dancing
- 0of them about dancing
Part 01
Keep the evidence, not just the answer
Prevents the un-debuggable catalog and the confident wrong overwrite. Earned its keep when a rented listening service was 85% accurate alone and right 32% of the time when it disagreed with the title. Applies to sensor fusion, address checking, merging vendor feeds, and anywhere a status column has been overwritten and regretted.
Part 02
Let “I don't know” be an answer, and route it
Prevents silent wrongness at scale and review queues that grow faster than they drain. Earned its keep at the channel door (3,000 decisions covering 4.5 million videos) and in the two-letters-apart dancer names that a threshold would have merged or split wrongly. Applies to moderation, document classification, deduplication, and every “misc” bucket.
Part 03
Keep the batch machine honest
Prevents un-deployable jobs, walks that skip rows, per-request model costs, and regressions with no name. Earned its keep every night at seven, and in the ninety-one champions and eleven search queries that fail the build if a rule change breaks them. Applies to every backfill, re-index, and integration you will ever write.
Part 04
Let people in without letting chaos in
Prevents two truth systems that disagree, vandalism, empty backlogs, and rewritten history. Earned its keep in dancer-owned pages with tour dates while every performance credit stayed in the notebook. Applies to business listings, author profiles, marketplace moderation, and any registry of people or firms.
Part 05
Spend a small budget where it counts
Where to start tomorrow: add the notebook. Everything else in this series becomes possible once every opinion is a row with a source and a grade.
Take-aways, without the tango
- 01Keep every opinion as evidence with a source and a grade, and let agreement rather than confidence make a fact.
- 02Let “I do not know” be an answer, refuse in the band where thresholds are least reliable, and route what is left to a person.
- 03Put the human decision where one judgement covers the most rows, and work in piles by reason rather than one queue by age.
- 04Make batch work short, resumable and scoped, store what the source said, and do expensive judgement offline as a file.
- 05Turn every production mistake into a test, so a fixed bug cannot come back.
- 06Treat a user as one more witness in the same record, and let the subject own the facts about themselves but not the evidence.
- 07Count the ambiguity before you model it, spend the inventory you already hold, and write the reason beside every constant.