Top all-time · #13744
Serge Skoredin
Personal blog · skoredin.pro/blogprogrammingsystems
Serge Skoredin's personal blog at skoredin.pro covers programming and systems. Since 2025, 5 different Hacker News readers have linked it 22 times, most often “Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production”. It is still writing: the last post was on 2026-09-16, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
HN readers link this blog as an example of write-ups that dig into why memory leaks and performance issues happen, shared alongside michellh's Ghostty internals posts in a thread on Ghostty's memory leak.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Senior Go developer with 7+ years experience. From bartending to building scalable backend systems. Berlin-based, working globally.
Most-linked posts?
- Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production3 people · 3 mentions · first linked 2026-01-10
- Event Sourcing in Go: From Zero to Production2 people · 2 mentions · first linked 2025-11-18
What Hacker News says?
There are times where is just makes sense to read, measure and really understand why leaks, bugs and performance issues happen and vibe-coders will get stuck on this very quickly. This excellent write-up from michellh explains the issue in depth and all his blogs in building Ghostty are a recommended read on the Ghostty's internals. Similarly, these write-ups are a great read. Here is another one that documents a go…
Comment linking /blog/golang/goroutine-leak-debugging
on “Finding and Fixing Ghostty's Largest Memory Leak”Submitted CPU cache-friendly data structures in Go as a story · 193 points
HN discussionSubmitted Event Sourcing in Go: From Zero to Production as a story · 60 points
HN discussionSubmitted Ring Cache for High-Frequency Trading in Go: Microsecond-Level Data Access as a story · 8 points
HN discussionSubmitted Observability in Go: What Goes in a Metric, a Log, and a Trace as a story · 4 points
HN discussionSubmitted Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production as a story · 3 points
HN discussionSubmitted Hexagonal Architecture in Go: Why Your "Clean" Code Is a Mess as a story · 3 points
HN discussionSubmitted Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production as a story · 3 points
HN discussionSubmitted Cutting JSON Parsing CPU Cost in Go as a story · 2 points
HN discussionSubmitted Building a Blockchain in Go: From Basics to Production Performance as a story · 2 points
HN discussionSubmitted Event Sourcing in Go: From Zero to Production as a story · 2 points
HN discussionSubmitted Building Feature Flags System: From Simple Toggles to Complex Rules as a story · 2 points
HN discussionSubmitted Go Memory Model Deep Dive: What Every Go Developer Must Know – Serge Skoredin as a story · 2 points
HN discussionSubmitted SQL vs. NoSQL vs. Columnar: Choosing the Right Database for Your Go Service as a story · 1 points
HN discussionSubmitted gRPC Streaming: Real-Time Communication That Works as a story · 1 points
HN discussionSubmitted Go Memory Model Deep Dive: What Every Go Developer Must Know as a story · 1 points
HN discussionSubmitted Building a Plugin System in Go: Make Your Monolith Extensible as a story · 1 points
HN discussionSubmitted Make Your Monolith Extensible Without Microservices as a story · 1 points
HN discussionSubmitted Building DSL in Go: From Simple Rules to Complex Workflows as a story · 1 points
HN discussionSubmitted Distributed Tracing in Go: Finding the Needle in the Microservice Haystack as a story · 1 points
HN discussionSubmitted eBPF and Go in Production: Network Monitoring and Security as a story · 1 points
HN discussionSubmitted Building Feature Flags System: From Simple Toggles to Complex Rules as a story · 1 points
HN discussion