Web Development

I have been building sites with Hugo for years. I wrote my own theme, tuned my build pipeline, and deployed more static sites than I can count. But I rarely see a resource that captures the why behind Hugo as well as the how. Brian P. Hogan’s Build Websites With Hugo does exactly that.

Published by Pragmatic Bookshelf in 2020, this 154-page book is not a reference manual. It is a guided tour through building a real portfolio site from scratch. You install Hugo, create a theme, add projects and a blog, wire up data sources, and deploy the final result — all while learning Hugo’s mental model.

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.

After twenty years in web development, I’ve realized that the most dangerous thing in our industry isn’t a security vulnerability or a system outage — it’s creeping complexity. We are conditioned to believe that a more sophisticated setup equals a more professional output. We stack layers of abstraction until we can no longer see the foundation of our own applications.

I spent the first decade of my career as a “maximalist.” I wanted the flashiest IDE, the most complex build pipelines, and the latest alpha-version frameworks. But eventually, the weight of that tooling became a burden. I was spending 40% of my time fighting my environment rather than shipping code.

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.

AI Has Entered the Building

In 2026, the question is no longer “Will AI change software development?” but “How effectively are you using it?” AI tools have moved from experimental novelties to indispensable force multipliers. However, the sheer volume of tools — LLMs, IDE extensions, CLI wrappers, and autonomous agents — has created a paradox of choice.

This guide isn’t about the hype. It’s a pragmatic look at the current AI stack for developers, how to build a workflow that actually saves time, and where the “hidden costs” of AI adoption lie.