Things That Work So Well for Me I Can't Believe You're Not Using Them
summary
Describes concrete engineering practices: write requirements as BDD-executable scenarios so tests serve as HTML docs and acceptance gates; decide whether to build by measuring volume/variance and comparing costs (example €40k/month vs estimated savings); separate upload/reporting into modules or lambdas to protect the importer; apply a scientific method to production incidents (list hypotheses, verify to eliminate causes, avoid shotgun fixes); ensure observability during development (log every branch, add metrics like success/error counts and error-type distribution); and use baby-step TDD, sketch-and-refactor, and mob reviews.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:55Practices are contextual
- 7:10Prove automation value
- 11:42Design requirements
- 16:17Modules vs microservices security
- 24:23Coding when unsure
- 33:37Programming creativity sketches
- 41:01Observability in production
- 47:25Unit test logs clarity
- 48:52Mob code review
- 50:18Scientific bug method
- 53:47Summary & Q&A
related talks
01h 04mBuilding on Success, Beyond the Obvious
01h 05mMicrotesting
57mSetting a Good Example - How to improve your SbE, BDD & ATDD Artefacts
59mTechniques for writing high-quality code
28mYour Testing Strategy is broken - lets fix it!
25mAdopting a Test driven Mindset in the Workplace
14mThinking of Quality as developer productivity tool
38mHow Are We Supposed to Know what We Should Create?