Zuckerberg gray tshirt and coding guidelines
summary
Claim: enforceable coding guidelines cut decision fatigue, speed reviews and lower long‑term maintenance cost. Cites 35,000 decisions/day as the reason to eliminate micro‑choices, recommends adopting C++ Core Guidelines (or industry equivalents) and automating style with a pre‑commit formatter that reformats commits so reviewers stop flagging style. Mentions SonarQube for complexity metrics; reports the automated hook reduces style comments, eases onboarding, and shifts reviewer attention to architecture and tests.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:32How Many Decisions Do You Think an Adult Person Makes in a Single Day
- 1:45Agenda
- 5:43Why Coding Guidelines Are Good for the Reader
- 7:01The Maslow Pyramid
- 10:43Code Indentation
- 15:46Why Guidelines Are Good for the Management
- 22:43How Many Decisions We Make a Day
- 23:49Coding Guidelines against Decision Fatigue
- 24:20The Longest Function Possible in Your Code
- 26:37Automating Formatting
related talks
38mCracking the Code Review: from Guesswork to Automated Guidance
24mKeynote – Michael Feathers
52mThe Zen of Programming
01h 03mDeveloping C++ @ Facebook Scale
54mReadable Code: The Secret to Clean, Productive Software
40mDo we need it?
38mImplementing a Strong Code-Review Culture
50mThe Effective Developer - Work Smarter, Not Harder