Understand before optimizing
Most performance and cost problems are really understanding problems. I start by making the system legible.
About
Software engineer, founder and lecturer, working between backend systems, cloud infrastructure and the people who run them.

I am an independent technical consultant working on backend systems, cloud infrastructure and integrations. I work with small and medium-sized companies that need to understand what they run, control what it costs and change it without breaking production.
I also build and maintain my own software products. Building them keeps me close to the same problems I diagnose for clients: unclear systems, risky releases and knowledge that lives in one person's head.


Most performance and cost problems are really understanding problems. I start by making the system legible.
I prefer simple, observable systems over clever ones. Good architecture protects business rules and data first.
Decisions, trade-offs and plans get written down, so the team can keep going without me.
I say when something is outside my scope, and I do not promise results I cannot control.