// Topics / Golang
Golang
Definition
Golang coverage in this archive spans 17 posts from Nov 2016 to Apr 2025 and leans into practical engineering craft: interfaces, testing, and maintainable implementation details. The strongest adjacent threads are ai, architecture, and backend. Recurring title motifs include go, ai, practice, and patterns.
Key claims
- The through-line is clarity first: simple designs that survive change beat clever abstractions.
- Early posts lean on go and stopped, while newer posts lean on go and event as constraints shifted.
- This topic repeatedly intersects with ai, architecture, and backend, so design choices here rarely stand alone.
Practical checklist
- Keep interfaces small, automate regressions early, and make operational assumptions explicit in code.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read ai and architecture before committing implementation details.
Failure modes
- Abstracting before usage patterns are stable enough to justify indirection.
- Treating style consistency as optional until quality and velocity both degrade.
- Applying guidance from 2016 to 2025 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): Testing AI Where It Actually Runs
- Then read (operating middle): Feature Flags at Scale: What Nobody Warns You About
- Finish with (foundational context): Why We Chose Go for Our Backend Services
Related posts
- Testing AI Where It Actually Runs
- MCP in Practice: Building Tool Servers in Go
- AI Code Review Is Mostly Noise
- Reasoning Models in Production: A Practical Guide
- Go Concurrency Patterns I Use in Every Service
- TypeScript: A Go Developer’s Honest Take
- OpenTelemetry in Late 2021: What’s Ready and What’s Not
- Event Sourcing in Practice: What I Learned Building Financial Event Pipelines
References
17 entries tagged “Golang”