Make the next step obvious.
Useful feedback, readable status, and a clear path through a task. An interface should help people understand what just happened and what comes next.
From the way a screen feels to the way a system handles failure.
I’m developing my practice across web interfaces, APIs, and databases. These projects are a place to connect product ideas with the engineering decisions that make them work.
My current focus is full-stack web development, with a growing interest in backend reliability. I use AI-assisted development as part of that process and am continuing to deepen my understanding of the systems I build.
Web applications · Database integrity · Observable workflows
Three principles reflected
in these projects.
Useful feedback, readable status, and a clear path through a task. An interface should help people understand what just happened and what comes next.
Booking conflicts belong in database constraints. Delivery state belongs in a persistent queue. The interface is one part of a complete workflow.
Activity records and attempt histories turn hidden behavior into something that can be inspected, understood, and improved.