Using Empathy to Make Tests Easy and Code Safe
summary
Claims that empathy-driven refactoring — specifically Naming as a Process plus Arlo Belshee’s risk tagging — makes unsafe code incrementally testable and dramatically reduces reading time. Method: repeatedly extract definition and rename definition through stages (obvious nonsense → honest → completely honest), applied to a contract example; after about 20+ renamings the contract becomes readable, reveals an obvious IP-claim bug, and proves the approach both practical and faster over repeated iterations.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:48Business problems and legacy code
- 5:59Panic and illusion of control
- 8:25Refactoring and empathy
- 10:11Naming for readability
- 17:13Honesty in naming
- 19:40Refactoring as empathy
- 21:06Resources and closing
- 22:09Q&A
