DEVELOPER NEWS STREAM
Direct logs, engine updates, and framework notifications parsed from curated RSS feeds and announcements, updated hourly.
Pavan KumarI built a Go library to solve a problem Python solved in 2002
I want to preface this by saying this is not a "look what I built" post. This is more of a "I kept...
Daniel WestgaardHow to Find Every Consumer of Your Go Module
You maintain an internal Go module. A breaking API change is coming. Which repos across your org import it — and at which version? Here's why the a...
Yogesha KSnakes & Gophers — A Python Dev's Guide to Thinking in Go
You've written Python for years. Now you're picking up Go. This isn't a tutorial — it's a guide to rewiring your instincts.
Harrison GuogRPC Interceptors in Production: Design Patterns That Survive Real Load
gRPC interceptors are where cross-cutting concerns live — auth, tracing, retry, metrics, rate limiting. Most examples online show toy single-interceptor demos. Production systems need to stack, order, and compose them correctly. A practical guide.
Harrison GuoGo Generics, One Year In: Which Promises Held, Which Didn't
Go 1.18 shipped generics in March 2022. Four years later, the honest picture: they're useful for a narrower set of problems than the community hoped, they fit naturally in a few places, and overuse them and your code gets worse. A production retrospective.
Harrison GuoIronSys: A Production Blueprint for Modern Concurrency
After Four Pillars of Concurrency, the natural question: what does a system actually look like when it uses all of them deliberately? IronSys is a composite blueprint — the concurrency architecture I'd build today if I were starting over, with the trade-offs each choice buys.
Harrison Guosync.Pool in Go: When It Actually Helps, and When It Quietly Hurts
sync.Pool is the Go feature most likely to be used incorrectly. A working engineer's guide to when pooling buffers actually saves GC pressure, when it just adds complexity, and the benchmark methodology that tells the difference.
Harrison GuoGo Profiling in Anger: pprof, Escape Analysis, and Inlining Without Magic
Most performance advice for Go is ritual — 'use sync.Pool,' 'avoid interface boxing,' 'preallocate slices.' Useful sometimes, hollow often. A production engineer's guide to profiling Go systems with pprof, reading escape analysis output, and understanding when the compiler actually inlines.
Andrei MerlescuFrom Zero to Hero: Building a Key Issuance Server with `verbose` and `figtree`
In August 2024 Andrei Merlescu wrote a package called verbose and released it under the Apache 2.0...
Olivia Craft8 Cursor Rules for Go Developers — 2026 Edition
Eight Cursor rules that make your AI write idiomatic Go — proper error handling, accept interfaces, context-first signatures, owned goroutines, directional channels, no init() tricks, table-driven tests, and lint-clean commits.
Juan Carlos Garcia EsquivelGuía Definitiva de Merge Sort: El Algoritmo de Divide y Vencerás
Merge Sort es un algoritmo de ordenamiento basado en el paradigma Divide y Vencerás. Divide...
Bala ParanjThe Most Important Refactoring Was Deleting 500 Lines I Was Proud Of
How I deleted a generic Pipeline[T] framework and a pass-through workflow layer, and why the codebase...
Ortiz de Arcanjo António DavidPor que o seu Microserviço deve permitir Integração via JSON-RPC?
Embora o REST seja o padrão absoluto para o Frontend, a comunicação entre serviços...
Viktor LogvinovSimplifying Reactive Component Frameworks in Go: A Signal-Based Architecture for Cross-Platform Responsiveness
Introduction Developing reactive UIs in Go has long been a double-edged sword. On one...
Orim Dominic AdahGo Templates Snippets for VSCode
I started learning how to use Go templates about a year ago and I found it arduous to stressful to...
Odilon HUGONNOTCQRS in Go — Part 1: the aggregate, Transition() and the Clone() you forget
How to structure a CQRS aggregate in Go: value struct, Transition() returning a new state, mandatory Clone() for collections. The shared slice trap.