Staying in Control
summary
Argues that actual value comes from runnable, reusable pieces that set a system to a known state: programmatic controls that create example accounts, rooms and timers, a controls namespace that composes examples, a diagnostic substitute to spy on identifier side effects, and simple GET-based control URLs to seed UI state. Demonstrates handler-pattern dependency injection, a mail‑catcher inbox for test emails, and UI toggles (turn off access control) — demos run and expose coupling and reuse issues.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:09Software engineers?
- 4:37Scientific method in SE
- 6:29Software controls
- 11:24Designing controls
- 13:10Live demo: programmatic controls
- 17:48Demo: web UI controls
- 25:54Scripts and UI controls
- 32:42Style guides and system controls
- 35:13Controlling email and external systems
- 36:16Best practices for controls
- 39:49Scientific thinking beyond code
- 41:16Resources and closing
