Things I Find Myself Repeating About Go
summary
Practical, specific rules for production Go: concrete naming guidance (shortest name that captures purpose, package names that state what they provide), initialization patterns like initialize once and only once, use of helpers for decoding and testing (custom UnmarshalJSON for variant fields, dumpBody type with String for lazy eval), prefer guard clauses and keep to the left selection style over nested if/else, use main.run pattern and a worker group to start, monitor and gracefully stop goroutines as a unit.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:04The importance of naming in Go
- 10:56Initializing variables once
- 16:10Keep to the left pattern
- 19:43Using helpers for clarity
- 29:41Go routine management
- 33:12Summary and closing thoughts
