How I Build

I enjoy building things that are meaningful.

Sometimes that’s a website. Sometimes it’s a CMS integration, a design system, an internal tool, or a workflow improvement that nobody outside a company will ever see. The technology changes from project to project, but the way I approach building things stays pretty consistent.

Start with understanding

Before I think about frameworks, architecture, or implementation details, I want to understand the problem.

Questions like:

The more clearly I understand the problem, the simpler the solution usually becomes.

Build for the people who maintain it

I’ve worked on projects with a handful of pages and others with nearly a hundred. I’ve inherited systems built by other developers and returned to code I wrote years earlier. One thing I’ve learned is that software spends far more time being maintained than being built.

I try to create systems that are:

Clever solutions are fun to write once.

Clear solutions are useful for years.

Performance matters

I care a lot about performance because users notice it immediately, even if they don’t know why: a fast experience feels polished and slow experience feels broken. Whether it’s improving Core Web Vitals, reducing layout shift, optimizing assets, or simply shipping less JavaScript, I try to make performance part of the process rather than something that’s addressed at the end.

Accessibility is part of good engineering

Accessibility shouldn’t be treated as a separate concern or afterthought. Semantic HTML, keyboard navigation, screen reader support, focus management, and clear content structure aren’t extra features. They’re part of building quality software.

The web works best when it works for everyone.

Content deserves good tools

A lot of my favorite work has involved helping content teams. I’ve spent years working with Contentful and other headless CMS platforms, building custom applications, integrations, and editorial workflows. The most successful systems aren’t always the ones with the fanciest frontend. They’re the ones that help the people maintaining content do their jobs efficiently and confidently.

Build systems, not just features

I often look beyond the immediate task. If a problem keeps happening, I’d rather understand why than keep fixing symptoms.

That’s one reason I enjoy things like:

Stay curious

One of the things I love about technology is that there’s always something new to learn. Some years that’s frontend architecture. Other years it’s performance optimization, data workflows, AI tooling, or a completely different skill set. Lately I’ve been spending more time learning about data analysis, Power Query, and Excel alongside the web technologies I use every day. I don’t think learning ever really stops. That’s part of what keeps this work interesting.

What I’m aiming for

At the end of the day, I want to build things that are useful and enjoyable.

If users can accomplish what they came to do and the people maintaining the system aren’t fighting against it, that’s usually a good sign that I’ve done my job well.

Related Links

 GitHub LinkedIn CodePen