Blog
Next.js 16 caching, finally explained like a normal person
Cache Components and the 'use cache' directive replace years of confusing caching rules with one simple question: how fresh does this part of the page need to be?
Server Actions feel private. They aren't.
Next.js Server Actions look like ordinary functions, but every one of them is reachable from the internet. Here's the mindset shift, and a checklist to keep them safe.
You probably don't need that useEffect
The most misused tool in React, explained with everyday examples — and the simpler patterns that replace it in most cases.
Node.js grew up — you might not need all those packages
Node.js now does out of the box what used to require half a dozen npm packages: fetching data, running tests, reloading on changes, reading .env files, even TypeScript.
"use client" does not mean what you think it means
A plain-English explanation of React Server Components — where your components actually run, and why the naming confuses everyone.
Do you even need React for that?
React is the default choice for everything web — but for a lot of everyday widgets, the browser's built-in Web Components are simpler, lighter and future-proof. A follow-up to my intro to Web Components.
Intro to the Web Components
Learn how to create your first vanilla JavaScript web component.