Ten Angry Comments Later: Stories About Code Reviews, Teams, and Yesterday’s Code
summary
Stories show concrete fixes and failures: a VAT change from 19% to 16% reveals missing date logic, a reviewer throws away a finished library instead of iterating, and one team builds a Vaadin Roots Export Maven Plugin to keep framework standards while preserving an overview. The workflow rules are specific — use the two-loop rule then talk, prefer short pair sessions over rewrites, and ship small improvements with 32 commit cards to nudge quality without blocking delivery.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 2:24Coding is not just coding
- 4:51Collaboration over perfection in code reviews
- 8:25Handling negative feedback constructively
- 12:47PR ping pong and timely communication
- 16:02Using emotion effectively in feedback
- 18:30Legacy code and emotional ownership
- 23:37Scope decisions in pull requests
- 27:33AI communication vs human collaboration
- 30:26Summary and key takeaways
