Tidy First?
summary
Thesis: software design is an exercise in human relationships, primarily between waiters vs changers and among changers themselves. Practical claim: sequencing and splitting work into tiny behavior or structure PRs (never mixing the two) reduces variance of delay, makes behavior changes reversible and structure edits low‑risk, and enables backward‑compatible API migrations. Concrete tactics: extract helpers, phase API implementation behind old APIs, ship small reversible refactors, then deliver the final visible change — make the change easy, poof.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 0:45Human relationships in software design
- 6:35Software design enlightenment
- 15:02Conclusion
related talks
36mProgramming Is the Easy Part
54mKeynote – Kent Beck
30mWhy should I write software well?
01h 10mKeynote: Strategies to Cope With Conflicting Design Patterns in C++ Development Teams
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
25mTransforming legacy software
33mClosing Keynote
56mThe art of keeping your project from falling apart