How did you end up becoming a developer?
My path into development wasn't exactly the normal route. It probably started as a kid, experimenting with CGI software on my first device. That, combined with A-level Media Studies, got me heavily into design and 3D, and the tech behind it.
Alongside this, I was always trying to build websites with platforms like WordPress (with much frustration), which led me to teach myself HTML, CSS and JavaScript instead. I kept building on that, from making my own software and websites to experimenting with JavaScript and Python in After Effects and Blender.
With programming, there was always something new to learn, and that gradually drew me towards development. I carried on throughout my Media Production degree, often mixing the two worlds together. In my second year, I did work experience at an agency where Josh was lead developer. By graduation, I'd decided to pursue software development, and Josh had set up DEXM.
What does your typical day at DEXM actually involve?
It's difficult to define a 'typical' day. We often have several projects spanning months on the go at once, alongside website maintenance, updates and new projects coming in. Sometimes I'll spend weeks on the same project, while other times I'll be switching between projects every day.
We also try to set aside time for learning and for our internal tools. Most of that gets spent on tools like our project management and website management toolkit, which is also a bit of a playground for experimental technology we might roll out to real projects in future. Other times it's Umbraco courses and working towards certifications, or researching newer tech that could benefit our projects and clients.
You studied Media Production before moving into development. What from that background still influences the way you build things?
Having a bit of a design eye is always useful in development. Security, scalability and functionality are paramount, and user experience and a clean interface are just as important.
A website also brings together lots of different media, from copy, video and photography to motion graphics and illustration. Understanding these, and how people consume and interact with them, really helps when building a site.
Creating mockups and design elements for the DEXM website is also a good excuse to keep my Adobe and Blender skills up to scratch.
When you first look at a new website or app, what's the thing you notice before everyone else?
Mainly, how much AI has been given the reins on the design decisions. There are usually a few dead giveaways.
Aside from that, I always keep an eye on loading speed, user experience and the quality of the content. It's also nice to come across a really well-made site and think, 'Yeah, some real care and expertise has gone into that.'
"Set a high standard" is something we talk about a lot at DEXM. What does that actually mean to you when you're designing or building something?
To me, it means building something to the highest possible quality, and that covers quite a few things: a clean codebase, documentation that's easy for both humans and AI to understand, great UI and UX, a balance of essential and nice-to-have features, and proper security.
Doing all of this efficiently matters just as much, with plenty of thought going into the architecture and how the project will actually work before development even begins.
How has AI actually changed the way you work? Not the hype, just the useful stuff.
I was fortunate to learn to code just before the first mainstream AI tools like ChatGPT came out. Now, AI is almost like having a team of other developers to direct, handling much of the boilerplate and repetitive code. It's also a great learning resource, letting me review code and better understand how it works and why.
Some of the most successful uses of AI have actually been inside the systems we build for clients, and in our own internal tools. Adding an AI layer can save countless hours that would otherwise go on mundane background tasks. Interestingly, the best use of AI is rarely as simple as adding a chatbot.
We've recently acquired a 3D printer. What have you printed so far, and how quickly has it descended into printing completely unnecessary things?
I think we've all printed our fair share of both cool and useless models, from buttons, car parts and branded office tools to miniature cats, lightsabers and skateboard-riding cartoon fruits. I'm sure there's much more to come now that we've got our Halloween orange and Christmas red filament.
What's something you've built at DEXM that you're particularly pleased with?
The aim is to be pleased with every project, but one I'm particularly proud of is our Umbraco Setup Wizard. It's an internal tool that guides the team through setting up a new client website, covering everything from cloud hosting and code to branding, integrations and domains. It keeps things consistent and makes sure nothing important gets missed.
On the client side, some of my favourite work has been on our larger business software projects, several of which are now getting close to going live.
Is there a technology you were sceptical about but have since changed your mind on?
Definitely vibe coding platforms. Security is always a concern when there's little to no human oversight, and the interfaces can often feel quite cookie-cutter.
That said, we've found these platforms can be a great way for entrepreneurs to bring their ideas to life and build working prototypes. When they bring those to a developer, it can cut out a lot of the early back-and-forth over the spec. Having a concept that's already halfway there gives the developer more time to make it secure, scalable and efficient, and to refine the UI and the overall experience.
What have you learned since joining DEXM that you didn't expect to?
I hadn't done much backend development before, so learning SQL Server has been a big one, along with exploring new frameworks and getting into building MCPs. Being able to create my own models for the 3D printer has been a fun bonus too!