Search across blog posts and diary entries
Blog/Tag
6 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.
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.
Time complexity is the difference between code that handles a million users and code that crashes with a thousand. It is one of the most important concepts in software engineering and one of the most poorly understood outside of interview preparation. Here is the version that actually sticks.
You use them every day. They power everything from database indexes to programming language runtimes to the fraud detection systems at your bank. But most developers treat hash maps as magic. Here is what is actually happening inside one.
Everyone tells you to be good at math for computer science. Almost nobody explains why in a way that connects to real work. Here is the honest version: what the math actually does, where it shows up, and why the underlying reasoning matters more than the equations themselves.
Two of the most influential programming languages ever built. One gives you total control over the machine. The other abstracts the machine away entirely. Both have been building the world's most critical software for decades. Here is how they actually compare, and when each one is the right answer