Model the data first
Schemas, constraints and relationships get pressure-tested before the interface is built. Most rework I see starts with a data model nobody challenged early.
Profile
About me
How I work, what I care about, and the tools I reach for when a product needs to survive real users.
Operating principles
How I build
The decisions I make before writing code, and the habits that keep a system understandable after launch.
Make failure visible
Loading, empty and error states are part of the product. A failure that happens silently is still a bug, even when the happy path looks perfect.
Ship vertical slices
A thin path from interface to database beats a broad layer that is only half finished. Every slice is demoable, reviewable and safe to deploy.
Measure before optimizing
I profile before I refactor. Query plans, traces and Core Web Vitals decide where the effort goes, not a hunch about what feels slow.
Working with me
- Async-first communication with written decisions, so context survives time zones.
- Small, reviewable changes instead of one large hand-off at the end.
- Explicit trade-offs: what we are optimizing for, and what we are deliberately not doing.
- Documentation and handover included, so the system is not dependent on me being in the room.
