Most Go developers can recite one fact about the garbage collector: it exists, and it mostly works. That is usually
Continue readingGo’s Garbage Collector: Tricolor Marks, Write Barriers, and the Green Tea Era
Every API that survives long enough faces the same moment: a requirement lands that cannot be expressed as an additive
Continue readingAPI Versioning: How to Change a Live API Without Breaking Every Client
Every Go service that talks to PostgreSQL sits on top of a pool, and almost every incident review that mentions
Continue readingConnection Pooling Is a Queue: Sizing pgxpool Against PostgreSQL’s Process Model
Every allocation your program makes is a promise the kernel keeps lazily. When you write make([]byte, 512<<20) in Go, you
Continue readingVirtual Memory Is Deferred Work: Page Faults, RSS, and Why Allocation Numbers Lie
Whenever your backend fetches a URL that a user influenced — webhook targets, import-from-URL features, URL previews, PDF generators, RSS
Continue readingSSRF Defense That Actually Holds: DNS Rebinding, Redirects, and Cloud Metadata
Mixture-of-Experts models dominate the frontier right now, and almost every explanation stops at the same level: “a router picks a
Continue readingInside MoE Routing: How the Gate Decides Which Experts See Your Token
Every latency dashboard has the same shape: a line for the average request duration and a line for p99, with
Continue readingPrometheus Histograms and Percentiles: Measuring Latency Without Lying
Every relational database ships an isolation level selector, and most applications pick whatever the default is and move on. That
Continue readingSnapshot Isolation and Write Skew: What Your Database Actually Promises
The most expensive lie a system can tell is that it accepted work it cannot process in time. It usually
Continue readingBackpressure: What Your System Should Do When Consumers Fall Behind
Every language-level sync.Mutex rests on a guarantee the operating system makes for you: if a thread dies holding the lock,