Today I’m launching Golang Perf — a newsletter for engineers who want to really understand how Go works under the hood and how to make their programs faster, leaner, and more predictable in production.

Why performance?
Go isn’t just “easy to write”; it powers real infrastructure — microservices, distributed systems, internal tooling, networking stacks, and a ton of CLI tools. And once you go beyond the basics, you quickly run into the real stuff: goroutine scheduling, escape analysis, inlining decisions, GC behavior, synchronization costs, allocator quirks, and the ways all of that affects latency and throughput.

If you care about those details — or want to — this newsletter is for you.

What I’ll be writing about:

• Go runtime deep dives: compiler optimizations, escape heuristics, GC changes, scheduler behavior. Practical examples, not theory for theory’s sake.

• Profiling & debugging guides: making sense of pprof, trace, benchmarks, memory profiles — and how to actually fix what they reveal.

• Real production case studies: problems I’ve seen in the wild + what actually fixed them.

• Benchmarking workflows: how to measure performance correctly so your numbers mean something.

• Experiments & tools: code snippets, small utilities, interesting runtime findings, and things I break on purpose to see what happens.

My goal is simple: bridge the gap between “Go is fast” and “I know why it’s fast — and how to make it faster.”

If that sounds interesting, feel free to subscribe and share with other Gophers.
First issue is coming soon.

— Aslan