Skip to main content

Web Development

The Story

After more than 20 years working in web design and over a decade in professional web development, I’ve had the chance to see the web evolve through countless trends, tools, and frameworks.

Along the way, I discovered that my real niche sits in the realm between design and development — as a prototyper.

Photo of me kneeling down next to bright green grass in a garden, there is a wooden fence in the background. I am wearing a white Halo pride short sleeved t-shirt and white ripped jeans, my left arm is exposed showing me Halo glyph tattoos. My hair is the focal point of the photo, being a mixture or bright colors. Orange, Green, Yellow and Pink.

Prototyping is where ideas stop being abstract and start becoming tangible. It’s the space where rough concepts turn into something you can click, test, and refine. Working in this in‑between layer means translating visual intent into functional reality, often quickly and imperfectly, but always with momentum. It’s about enabling conversations rather than settling them — giving teams something real to react to.

One of the things I enjoy most about this role is rapid iteration. Requirements shift, designs evolve, priorities change — and that’s not a problem to be solved, it's just how development works in practice. Being able to respond fluidly, make adjustments on the fly, and explore alternatives without heavy overhead is where prototyping really shines. Over the years, I’ve explored a wide range of technologies, frameworks, and tooling. Each has its place, and many are incredibly powerful.

A close-up photo of a laptop keyboard and screen, with the focus on the keys and a blurred code editor open on the display.

Time and again, I find myself coming back to the fundamentals: HTML, CSS, and JavaScript. There’s a simplicity and directness to working close to the platform that’s hard to beat. No abstractions getting in the way — just ideas, structure, behaviour, and feedback. Using these core technologies allows me to move quickly, stay flexible, and focus on the problem rather than the tool.

Whether it’s validating a design direction, exploring an interaction, or bridging the gap between design and engineering, the goal is always the same: bring ideas to life as efficiently and clearly as possible. In a world that often chases complexity, there’s something reassuring about building with the simplest tools available — and using experience to know when that’s more than enough.