DEVELOPER NEWS STREAM
Direct logs, engine updates, and framework notifications parsed from curated RSS feeds and announcements, updated hourly.
Gabriel AnhaiaRetries and Backoff in Go: Where They Belong in a Hexagonal Service
Exponential backoff with jitter in Go belongs at the adapter, not the domain. Respect context deadlines, retry the right errors, keep the port clean.
Gabriel Anhaiagoogle/wire in Go: Compile-Time DI for Hexagonal Services
google/wire builds your Go dependency graph at compile time. Provider sets, generated injectors, and ports wired to adapters with no reflection.
Gabriel AnhaiaA Logging Port in Go: Keeping slog at the Edge of Your Hexagon
Import slog in your Go domain and you weld a logging library to your business rules. A narrow port keeps it at the edge, where it belongs.
Gabriel AnhaiaThe Transactional Outbox in Go: Reliable Events Without a Message Broker
Emit events in the same transaction as your state, then relay them with a Go poller. At-least-once delivery, no Kafka, no dual-write bug.
Gabriel AnhaiaInjecting a Clock in Go: Testable Time in Your Hexagonal Domain
Kill time.Now() calls buried in Go business logic. A Clock port, a real adapter, a fake, and tests that stop flaking on midnight.
Gabriel AnhaiaNative Fuzzing in Go: Finding Edge Cases With go test -fuzz
Go ships a fuzzer in the standard toolchain. Write a fuzz target, seed a corpus, and turn every crasher into a permanent regression test.
Gabriel Anhaiagolangci-lint in 2026: A Config That Catches Bugs Without the Noise
A pragmatic golangci-lint config for Go: errcheck, govet, staticcheck, per-path excludes, and a CI gate that fails on real bugs only.
Gabriel Anhaiapprof in Go: A CPU and Heap Profiling Walkthrough From Zero
Wire net/http/pprof, capture a CPU and heap profile, and read the hot path with top, list, web, and flame graphs.
Gabriel Anhaiabenchstat in Go: Comparing Benchmarks Without Fooling Yourself
One benchmark run proves nothing. Use go test -count and benchstat to read the delta and p-value before you claim a Go speedup.
Gabriel AnhaiaThe Go Execution Tracer: Finding Latency the Profiler Misses
pprof shows you where CPU burns. The Go execution tracer shows you where goroutines wait. Here is when the tracer beats the profiler.
Gabriel Anhaiastaticcheck for Go: The Analyzer Rules That Pay for Themselves
The staticcheck SA, ST, and S rules that catch real Go bugs go vet misses, and how to suppress the false positives without going numb to them.
Gabriel Anhaiaencoding/gob in Go: Binary Serialization Built for Go-to-Go Services
gob is Go's own binary wire format for Go-to-Go RPC. When to reach for it over JSON, how to register interfaces, and the caveats that bite.
Gabriel Anhaiasignal.NotifyContext in Go: Clean Ctrl-C Handling in One Line
Drop the signal-channel boilerplate. Tie Ctrl-C to a context, wire graceful shutdown, and add a second-signal force-quit in Go.
Gabriel Anhaiagovulncheck: Scan Go Code for CVEs You Can Actually Reach
Most Go dependency scanners cry wolf. govulncheck traces the call graph and tells you which CVEs your code can actually reach.
Gabriel Anhaiaregexp in Go: MustCompile, Reuse, and the Performance You're Leaving Behind
Compile Go regexes once at package level, trust RE2's no-backtracking guarantee, and know when a hand-written scan wins.
Tran Long AnYour Go struct already describes your API. Let it write the docs too.
Your Go struct already describes your API. Let it write the docs too. If you build HTTP...