A CTO who stays close to the code and the field
I believe architecture, product and operations cannot be steered properly without staying close to the code, the users and the real-world constraints on the ground.
That's why I stay hands-on: I design and decide, but I also contribute directly to the build. It's the best way to keep technical choices honest and the product genuinely usable.
My role is often to connect worlds that struggle to understand each other: leadership, product, operations, finance, support and engineering.
What guides my work
Pragmatism
Solve the real problem, in the real context, rather than the ideal solution on paper.
Simplicity
Prefer the simplest architecture that holds up and stays maintainable.
Architectural restraint
Refuse needless complexity: every layer must justify its existence.
Product sense
Keep the user and real usage at the centre of technical decisions.
Results focus
Ship what creates value, and actually get it into production.
Close to the field
Stay in touch with operations, support and end users.