Code Reviews Using Art Critique Principles
summary
Applies formal art-critique steps to code review: establish rules and mandatory participation, require a pre-review checklist that insists on run relevant tests and documented setup, then follow four stages — description (inventory and consensus), analysis (how it integrates), interpretation (constructive suggestions) and judgment (ship or fix). Claim: this method makes reviews less abusive, improves observation skills and prevents legacy shocks. Example: a handheld programmable LED array is built and used successfully for lighting photos. No thumbs-up-only approvals.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:00Who is Stacey
- 1:50What are art critiques
- 2:15Why I started doing code reviews
- 3:05I can fix this
- 3:23My own methodology
- 5:35Happy accidents
- 5:46Goals
- 6:34Process
- 6:59Rules
- 7:47Respect
- 9:31Mandatory Participation
- 10:16PreCode Review
- 13:49Code Critique
- 17:45Analysis
- 19:54Opportunity
- 21:14Question
- 22:45Constructive Criticism
- 26:00Conclusion
- 27:25Questions
