Engineering before presentation
Architecture, resilience and a working product come first. Visual presentation matters, but it does not replace the engineering base.
Principles
These principles define the style of my engineering and product work: no corporate theatre, no artificial complexity, no anonymous responsibility.
Clarity over noise
A good system explains itself: in code, interface, documentation, release and operation.
Founder-level accountability
Responsibility should have a visible center. The more important the system, the less blurred accountability it should contain.
Systems over offices
Value is created by processes, code, infrastructure and people, not by office mythology.
Privacy by default
Data minimization, transparent processing, no unnecessary tracking and respect for user privacy.
Long-term infrastructure
It is better to build a system that outlives hype than a set of impressive but short-lived effects.