For over 15 years I’ve worked in web development, primarily as a front-end developer. For the last 7 years I've been building with WordPress. It’s where I've gained a lot of experience and delivered some of my most consistent work, across both theme development and plugins that extend functionality to meet project requirements.

I’ve led front-end builds, created component libraries, and worked closely with design, content and marketing teams to consistently ship maintainable, user-friendly sites.

Realising I Needed a Shift

But recently, I’ve realised that the direction I took, while solid, has also been limiting.

I didn’t set out to become “the WordPress guy.” It just happened. Saying yes to the work that came in, keeping things stable, and being relied on to deliver. And while I’ve learned a lot through that, I’ve hit a point where I want more: more challenge, more depth, more growth.

What I Want to Build With

That’s why I’ve been shifting toward the stack I actually want to work in; Laravel on the back end, React or Vue on the front.

Laravel fits the way I think about code: clean, expressive, well-structured. I’ve already built and deployed three Laravel apps for real users, all personal projects (not commercial), but very much production grade.

On the front end, I’ve used React in production, and Vue in smaller projects, and I’m building deeper into both. I care about structure, reusability, and momentum. Modern frameworks let me lean into all three.

Moving With Intention

I’m not starting from scratch. I’m shifting deliberately, with intent. This blog is part of that shift: a place to log what I’m learning, how I’m applying it, and where I’m headed next.

Let’s Chat

If you’re working with Laravel, React, Vue, or design systems, and especially if you’re hiring, I’d love to talk. Drop me a message and connect with me on LinkedIn.