Becoming a Better Curator of Your Code
summary
Argues for a curator mindset: treat code as an entrusted collection and make concrete changes that reduce future pain. Recommends adopting PEP8 or team-specific conventions, using tests as documentation (meaningful test names and grouped test classes like TestDrawShapes), write commit messages that state intent, run small refactors (group related variables into a class, simplify conditionals), apply the Boy Scout rule, remove dead code, and prefer mature libraries to hand-rolled solutions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:25About
- 4:14Curator
- 6:02Style Guides
- 10:13Tests That Document Code
- 11:13Documentation via tests
- 13:36Documentation Via Commits
- 15:46Team Discussion
- 17:43Boy Scout Rule - Examples
- 20:12Refactoring Examples
related talks
33mBuilding Code Quality
21mMaking the Most Out of Code Reviews
05mAn Effective Code Review
26m(Professionally) Coding with Others
25mBest Practices for Writing Clean and Maintainable Codes
18mBuilding a Culture of Code Quality
18mHow To Review Someone's Code While Not Being A Jerk!
40mCode Review - How to Do It Better?