Blog

Your endpoint is async but it still freezes the server. Here's the synchronous CPU work pattern that blocks Node's event loop and how senior devs catch it in review.

You've probably seen gRPC described as "REST but faster." That framing is technically true and practically useless.

Build an LRU cache from scratch: doubly linked list + hashmap for O(1) get and put, eviction by access order, and a bounded memoize wrapper on top.

Node.js has two module systems that don't interoperate cleanly. Here's how CommonJS and ESM work, how Node resolves imports, and how circular dependencies behave in each.

Nginx handles hundreds of thousands of connections with 4 cores. Here's why: event-driven epoll loops, 11-phase HTTP pipelines, pool allocators, and a master-worker model built for zero-downtime reloads.

"Our database is highly available" means four different things, and they protect against four different failures. A ladder for forcing that conversation to be specific — plus why the money most teams spend on availability goes to the failure modes they face least.

EJS, Handlebars, Pug and Nunjucks all do the same three things: tokenize, parse, compile. Build a real one — loops, conditionals, partials, escaping by default — and see exactly where HTML escaping stops protecting you.

Astro's JavaScript floor is zero; Next.js's is a framework baseline. That one architectural difference — hydration opt-in vs opt-out — decides most of this comparison, and it matters much less than it sounds once your users are logged in.

You've run git commit thousands of times. But have you ever wondered what actually happens when you do? Git isn't a file-syncing tool with version numbers bolted on.