How I work.

I started in graphic design, caring mostly about type and visual hierarchy. Around 2021 I realized design without code was half the job, so I moved into engineering.

Today I design and build web applications, from the interface to the data, integrations and deployment. The case studies here cover student onboarding, matching, billing and document workflows.

I'm most useful when a change crosses several parts of a product. I work through the requirements, make the tradeoffs explicit and follow the implementation through to a working release.

I use clear module boundaries, explicit data contracts and familiar tools so the product can change without losing track of its rules. A useful architecture makes the next change easier to understand.

I review progress through running software and explain what is implemented, what has been verified and what still needs work. Technical limitations and handover decisions belong in the record.

I use coding agents for scaffolding, refactoring, tests and reading codebases. I remain responsible for the architecture, business rules and the quality of the result.

When a feature interprets documents or helps someone make a decision, I check its output against explicit rules and examples. Uncertainty and the points that need human review should stay visible.