About
Business context and hands-on engineering belong together.
I am a systems-oriented software builder and consultant working across business processes, data, backend systems, integration and automation.
The work starts with understanding how things operate today, then finding the clearest and smallest useful change.
Professional bridge
A perspective shaped by how systems work in practice.
My experience around enterprise applications, operational processes, and data flows shapes how I approach systems today. I now combine that background with hands-on Python, backend, and data engineering, building on that foundation rather than replacing it.
That combination keeps attention on both sides of the work: how an operation functions and what a technical intervention needs to do to support it.
How I work
Judgment comes before implementation.
Understand before building
Start with the people, process, constraints and existing system before deciding what should change.
Separate facts, assumptions and hypotheses
Make clear what is known, what is being assumed and what still needs to be tested.
Respect software that already works
Keep useful software in place when it already does its job well.
Simplify before adding technology
Remove avoidable process complexity before encoding it in another system.
Integrate before replacing where sensible
Connect existing tools or automate the gaps when that is enough.
Prefer the smallest valuable intervention
Choose the most focused change that creates meaningful value and remains understandable.
Treat “do not build software” as a valid outcome
A clearer process or better use of existing tools can be the right recommendation.
Technical direction
Tools in service of understandable systems.
My current technical direction centres on backend and data engineering, with an emphasis on clear, testable and maintainable systems.
- Building
- Python, FastAPI, APIs
- Data
- SQL / PostgreSQL
- Delivery
- Docker, testing, CI/CD
Azure is a current learning and next deployment direction, not completed production experience.
Start a conversation
Tell me what isn’t working.
You do not need a technical specification, and you do not need to know whether software is the answer. Start with the process that feels awkward, repetitive, unclear or harder than it should be.
Discuss a problem