Exception Driven Design
summary
Argues that shipping without full test coverage is acceptable if three concrete pieces exist: a bug tracker that sends notifications like Flair so every 500 error includes request and user context, a repo and CI that allow fixes to be deployed in minutes, and client transparency about occasional errors. Embraces fail fast coding and isolating work like one job per email so failures surface immediately, treats each caught exception as a prompt to add a test, and calls out middleware and API routes as common blind spots.
AI-written summary · about
related talks
44mDependencies; Devil or Darling?
43mLearning to Live with Errors
42mTo TDD or not to TDD: that is the question!
49mExtreme Professionalism - Software Craftsmanship.
11mUse Case Driven Development
19mConsumer Driven Software Development
29mKeynote: BDD - Bias driven development
36mDesigning for failure - architecting fault-tolerant system