The Joy of Linters: Good Engineering Practices & Productivity Boosters
summary
Practical recipe for getting linters from theory into habit: use golangci-lint with a checked-in .golangci.yml, run linting in CI and on git diffs so only changed files fail, roll out in a three-phase rollout (default → local opt-in → full enforcement with a two-week trial), write tiny custom checks using go/ast + go/parser + go/analysis (example: ban time.Sleep), use automated fixes, and enforce formatting rules (gofumpt/gofmt, whitespace rules and a 120‑char line policy) across 77 microservices.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:00Why wont you get a linter
- 1:31What is a linter
- 4:56How to group your linters
- 5:29Quality vs readability
- 6:20Maximum pain theory
- 8:43New code base
- 10:51Preexisting code base
- 12:13The pain theory
- 13:55The hard bid
- 15:03The team
- 15:50Choosing a linter
- 16:59Intercustom linters
- 18:43Noslip Linser
- 19:25Custom Linser
- 20:07Lemon squeezy
- 20:49Summary
- 22:20Light stuff
- 23:29Max bits
- 24:54Python
- 27:17FormFree
