How to write pleasant code
summary
Argues for deciding on specific effects not abstract principles and demonstrates them: a single Presenter change can silently create an N plus one query that crashes production, so options are either split into an EmployeeListPresenter or add a guard like without_db that throws on unexpected DB access. Frames choices with human‑centered design — person context action — and shows how adding affordances and feedback prevents bad edits while staying out of the way for safe changes.
AI-written summary · about
chapters (7)
- 0:00Start
- 9:17What Failed
- 14:23Human Centered Design
- 18:13Context
- 20:40Adjusting to Other People's Context
- 21:29Social Environment
- 28:52Questions
