Opening keynote: Clear is better than clever
summary
Argues clarity matters more than style fights and gives concrete rules: use var for deliberate zero-values and prefer := for explicit initialization; prefer small, behavior-focused interfaces (change save(os.File) to save(io.Writer) and move closing elsewhere) and rename to reflect action (write). Use guard clauses and switch to keep success path visible, explicitly type uncommon requirements, avoid fallthrough, and rely on gofmt and fast builds to boost productivity. The claim is that these choices make code easier to maintain and test.
AI-written summary · about
chapters (13)
- 0:00Introduction to Clarity
- 1:06Software Engineering Defined
- 3:22Readability vs Clarity
- 5:29Variable Declaration Rules
- 7:23Initializing Variable Intent
- 10:58Exceptions and Conventions
- 13:20Interfaces for Behavior
- 18:55Line-of-Sight Coding
- 22:03Structuring Logic
- 25:19Core Values of Go Code
- 29:03Developer Productivity
- 32:21Conclusion
- 33:14Q&A Session
