about
i started programming in 2017, at sixteen, trying to understand how systems break. it took a while to realise that understanding how to break them meant first understanding how to build them.
since then the work converged on one class of problem: backends where being wrong is expensive. banking, asset management, insurance and payment infrastructure.
how i work
architecture is about trade-offs
not about frameworks, and not about folder structure. the discussion that matters is what you are willing to give up, and why.
measure before optimising
and say how you measured. a number without a methodology is not evidence, it is an anecdote. sometimes the honest measurement shows the change made no difference, and that is a result too.
model the domain first
the database is a decision that comes afterwards. a stable, clean core, independent of the tools around it, is what lets you swap those tools later.
make complexity invisible
without pretending it is not there. the simplicity a user sees is built on purpose, and somebody has to hold up what sits underneath.
craft
i like the idea of software craftsmanship, carefully. it describes the way of working well: attention to detail, ownership of what shipped, and the willingness to redo what came out wrong.
what it does not describe is the part that matters most in critical systems, which is engineering discipline. correctness, fault tolerance and reproducibility do not come from care, they come from method.
sequence
sequence is my independent engineering practice. it is how i take on services, run projects and build my own systems, focused on backend, financial infrastructure and integrations. when the work is mine, that is where it happens.
contact
available for senior and staff backend roles. remote-first, open to relocation.