The 7 Deadly Sins for Gophers
summary
Seven concrete mistakes with examples and fixes: overusing goroutines for trivial loops and doubling complexity, relying on panics instead of checked errors and preferring compile regex at startup over regexes that crash handlers, avoiding overengineering and unnecessary generics, renaming variables instead of useless comments, always wrap errors with %w to preserve context, prefer stdlib over heavyweight frameworks (Echo example) to reduce dependencies, and design libraries to expose useful pieces and not spawn goroutines internally.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:07Lust for Go concurrency
- 6:08Wrath of panicking
- 12:28Pride in over-engineering
- 18:06Sloth in unclear code
- 25:15Gluttony of unnecessary dependencies
- 33:06Envy of OOP in Go
- 39:46Pride in library design
- 46:58Complexity root of sins
- 49:27Q&A
related talks
26m7 sins of a Scala beginner
01h 43mCrazy Code, Crazy Coders
01h 29m“Simplicity: Not Just For Beginners”
31mDangerous Minds: How we're getting developer education wrong
35mThe League of Extraordinary Antipattern
05m10 Things Junior C++ Devs Don't Get
17mIf You’re Happy and You Know It (Inside the Mind of a Developer)
01h 31mLearning from C++ Juniors’ Mistakes