Frontend engineering
Interfaces that stay fast, accessible and maintainable as a product grows.
Technology
The technical depth behind the leadership.
Organised by capability, not by logo. These are the tools I build with and the ones I choose for the products and systems I lead.
Capabilities
Six areas of technical capability.
Grouped by what they make possible. No percentages or star ratings, just the stack as it is used.
Backend engineering
APIs, data models and business logic for systems that organisations rely on every day.
Mobile
Cross-platform apps from a single codebase, shipped to real users.
Cloud & deployment
Reliable hosting and release pipelines matched to the size of the product.
AI & intelligent systems
Practical AI where it earns its place: language interfaces, analysis and automation.
Architecture
System design choices that let software scale with the organisation using it.
Everyday toolingGit · GitHub · Postman · VS Code
How I choose
Principles behind the stack.
Technology decisions outlive the people who make them. These are the rules I use to keep them sound.
- 01
Proven foundations
Well-supported, widely understood tools for the core stack, so teams can hire, maintain and extend with confidence.
- 02
Simple until scale says otherwise
Start with the simplest architecture that works and add complexity only when real usage demands it.
- 03
Security and access by design
Authentication, roles and tenancy are designed into the data model from the first version.
- 04
AI with a job to do
Adopt AI where it removes real work or unlocks a capability, not as a label.
Engineering activity
Still shipping code.
A live view of GitHub activity over the last year.
Technical partnership
Choosing a stack or planning an architecture?
Whether it is a product idea, a business system that needs rebuilding, or a technology decision you want a second opinion on, I am glad to talk it through.