On Readable Code
summary
Argues that comments often signal bad code and encourage laziness, shows Sublime theme and an Adobe example where comments hide behavior, cites jQuery comments as useful for platform workarounds, reports a search finding 5 million TODOs across large open source projects, proposes to ban comments to force refactoring, demonstrates eye‑tracking that names alone don’t reduce cognitive load, and recommends short, referentially transparent functions with explicit types and putting todos into the backlog.
AI-written summary · about
chapters (4)
related talks
21mThe Art of Code Comments
41mTo comment or not
24m//TODO: Write A Better Comment
26m# TODO: Add Comments: 5 Tips for _Winning_ at Code Comments
18mHow To Review Someone's Code While Not Being A Jerk!
17mReady for Readable Code?
40mGood Code: What, Why, and How to Get There
20mGood Code is a Balancing Act