Search across blog posts and diary entries
Blog/Tag
5 posts
Every C programmer calls malloc, but few know what happens after the call disappears into the standard library. The allocator is managing a heap of raw memory, carving it into chunks, tracking what's free, and trying to do all of that fast enough that you never notice the overhead. Here's how it actually works.
Discord serves hundreds of millions of registered users, handles trillions of stored messages, and routes voice traffic through over 850 servers across 30+ data centers. None of that runs on a single clever trick. It runs on a stack that has been replaced, migrated, and rewritten in pieces as each layer hit its ceiling.
Most developers use these words interchangeably. They shouldn't. Concurrency and parallelism solve different problems, and mixing them up leads to code that's either over-engineered or broken in subtle ways.
Netflix streams to over 300 million subscribers across 190 countries, serves petabytes of video daily, and runs one of the most sophisticated engineering organizations in the world. Here is how they built it. Also, they rejected me. Three times. But we will get to that.
REST looks clean on paper. But beneath the surface, idempotency breaks, race conditions hide, and failures go silent. Here's what your API isn't telling you.