DEVELOPER NEWS STREAM
Direct logs, engine updates, and framework notifications parsed from curated RSS feeds and announcements, updated hourly.
Gabriel Anhaiatestcontainers-go: Real Integration Tests for Go Without Mocks
Spin up a real Postgres in your Go tests with testcontainers-go, get the lifecycle and readiness right, and keep the suite fast on every push.
Odilon HUGONNOTGo 1.25 testing/synctest: No More Flaky Concurrent Tests
time.Sleep in concurrent tests is a gamble. testing/synctest replaces the real clock with a virtual one inside an isolated bubble — deterministic, instant, no more CI timing failures.
Gabriel AnhaiaAccept Interfaces, Return Structs: The Go Idiom, Correctly Applied
Why Go functions should take abstract inputs and return concrete types, where the rule breaks, and the testing payoff it buys you.
Gabriel AnhaiaEffective Go in 2026: The Idioms That Still Decide Good Go Code
The Effective Go idioms that still separate good Go from bad in 2026: composition, small interfaces, error values, and sharing by communicating.
Akshay GuptaI just published Postgres MCP Server in Go!
I open sourced a project I have been building on the side: a Go MCP server that connects Claude Code...
Gabriel AnhaiaReflection in Go: The Few Times It Is Justified (and the Cost)
Reflection in Go is the slow escape hatch. Here are the few cases it earns its keep, the runtime cost, and when codegen beats it.
Gabriel Anhaiago:generate in Go: Code Generation Without a Build System
How go:generate, Stringer, and mockgen replace reflection and hand-written boilerplate in Go, and how to keep generated files honest in CI.
Gabriel AnhaiaVariadic Functions and the append(s, more...) Spread in Go: The Gotchas
Nil vs empty variadic slices, the shared-backing-array append trap, and the copy-when-you-must rules that keep Go slices from mutating each other.
Gabriel AnhaiaUsing defer to Modify a Named Return in Go (Carefully)
The defer-closure-over-named-return trick wraps errors and rescues cleanup failures in Go. Here is why it only works with named returns.
Gabriel AnhaiaBuild Constraints in Go: //go:build and Conditional Compilation
How //go:build, GOOS/GOARCH filename suffixes, and custom tags decide which Go files compile, and how to retire the old +build syntax.
Gabriel AnhaiaGo Maps Iterate in Random Order on Purpose. Here Is How to Handle It
Go randomizes map iteration order on purpose. Why the runtime does it, how it breaks tests, and how to sort keys for stable output.
Gabriel Anhaiapanic and recover in Go: The 3 Times They Are Actually Correct
Most recover() calls in Go hide bugs. Here are the three places panic and recover are the right tool, and the pattern that turns them into landmines.
Gabriel Anhaiavar _ Iface = (*T)(nil): The Go Compile-Time Interface Check You Should Use
One line of Go turns a silent runtime interface break into a build error. Where to put var _ Iface = (*T)(nil) so it actually helps.
Gabriel AnhaiaSentinel, Typed, or Opaque: Choosing an Error Style in Go
errors.Is sentinels, errors.As typed errors, opaque behavior-checked errors. How to pick one style per package boundary in Go.
![String and []byte in Go: The Conversions That Quietly Allocate](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftbyaitbz5a4jo46z8zmy.png)
Gabriel AnhaiaString and []byte in Go: The Conversions That Quietly Allocate
Every []byte(s) and string(b) copies memory. Here are the ones the Go compiler skips for free, and how to prove which is which.
Gabriel AnhaiaGo Slice Tricks: Insert, Delete, and Filter Without a Helper Library
In-place delete, insert, filter, and reverse in Go — plus the aliasing and memory-retention traps, and where the slices package covers you now.