I'm a software engineer at Smedley Group Advanced Technology, a global electric karting events company with operations in the UK and the US. I'm part of a small engineering team reporting to the Head of Advanced Technology. Small enough that every project means owning the problem end-to-end: understanding the domain, designing the system, deploying it, keeping it running.
The domain is motorsport; the discipline applies beyond it. What defines the work is less the technology stack and more the environment it demands. Every project begins with a domain I'm still learning, stakeholders with different mental models of the problem, and constraints that only surface once you start asking the right questions. The software comes after all of that.
I think carefully about engineering practice and whether it's producing real value. I'm sceptical of process adopted by convention rather than by reasoning, and I believe every architectural decision should have a rationale you can articulate clearly. If it doesn't, it isn't a decision; it's a default.
I'd rather spend a week understanding what to build than a month building the wrong thing. I develop fluency in unfamiliar contexts quickly, identify what the problem actually is before committing to a solution, and design systems that address the real constraint rather than the first one described. That is what I'm looking to bring to harder problems in new domains.
Outside the day job, I'm finishing a BSc in Computer Science at the University of East Anglia (86% average, expected June 2026). I write here about engineering practice, architecture, and the reasoning behind decisions. The archive is the front door, and the work history shows the practice behind it.
If anything here resonates, write. I read everything.