Opinion

The Hindsight of Two Decades

Twenty years in web development. Hundreds of projects. Dozens of technologies learned, mastered, and eventually discarded. If I could step into a time machine and talk to my younger self on day one, my advice wouldn’t be about the latest “hot” framework or a specific library. It would be about compound interest in knowledge.

The industry is noisier than ever. Every week, there’s a new “game-changing” tool that promises to make you 10x more productive. But here’s the cold truth: the most successful developers I know aren’t the ones who know the most frameworks; they are the ones who understand the fundamentals so deeply that they can pick up any framework in a weekend.

The Book That Changed How I See Websites

I have recently read Just Enough Design by Taku Satoh, a slim but powerful book published by Chronicle Books. Satoh is one of Japan’s most respected living designers — he has shaped everything from packaging for major brands to museum exhibits — and in this book he distills decades of work into a single idea: hodo-hodo (ほどほど).

The word is ancient Japanese. It means “just enough,” “moderation,” or “the right amount.” When Satoh applies it to his work, it becomes a design philosophy: deliberately holding back, leaving room for the person on the other side to engage with an object according to their own sensibility.

The Framework-First Fallacy

In the landscape of 2026, the default response to almost any web development project is to start with a framework. Need a personal landing page? Reach for Next.js. Building a simple data dashboard? Boot up a React template. Creating a documentation site? Gatsby or Nuxt is the presumed choice.

We have reached a point where many developers — especially those who entered the industry in the last five years — literally cannot build a website without first installing a framework. This isn’t just a shift in preference; it’s a Framework-First Fallacy that prioritizes the developer’s comfort over the user’s experience and the project’s long-term health.

The Tailwind Hype Is Real

Tailwind CSS has fundamentally changed how we think about styling in 2026. It has won the “CSS Wars” for a simple reason: it solves the specificity and naming problems that have plagued CSS developers since the mid-90s. No more debating whether a class should be .card-title-inner-wrapper or .c-card__header. No more worrying if changing a margin in one file will break a layout in three others.

However, its popularity has come at a cost. Tailwind is deceptively easy to start using, but incredibly easy to misuse. Most developers are treating it like “inline styles on steroids” rather than the constrained design system it was meant to be.

Opinion

What I'd Learn If Starting Today: A No-Nonsense Dev Career Roadmap Featured

The Hindsight of Two Decades

Hodo-Hodo: The Japanese Philosophy That Could Fix Web Design

The Book That Changed How I See Websites

Why Frameworks Are Overused (And How to Avoid It)

The Framework-First Fallacy

Why Most Devs Misuse Tailwind (And How to Fix It)

The Tailwind Hype Is Real