AI-native workflow
I use AI coding tools as leverage for speed and iteration — not as a substitute for judgment. I know when to steer, when to stop, and when to rewrite.
§ About
Technicalworkshouldbelegible.
I like building products where the surface has to be polished but the underlying system still has to stand up technically. That usually pulls me toward interfaces, AI-native tooling, data-heavy experiences, and machine-learning work that has to be explained to another human being, not just executed.
The portfolio is intentionally short. I’d rather show a few projects that reveal how I think than stack up many thin summaries. The F1 lab is the clearest example of the shape I enjoy most: product, frontend, ML, automation, and narrative all tied together.
§ 02 · About
Theworkshouldexplainitself.
This portfolio is meant to show more than finished visuals. It shows how I frame technical problems, build with AI assistance, and package the result so another person can understand it fast.
I'm most interested in work that sits between product thinking, frontend execution, and technical depth — interfaces, prototypes, tooling, and machine-learning projects that need to be both useful and legible.
Technical storytelling
I turn complex technical work into interfaces and narratives that a non-specialist can still understand quickly. Documentation is part of the product.
Product thinking
I shape the work around what an employer, user, or stakeholder needs to understand first. Craft is the default; shipping is the measure.
Snapshot
Focus
frontend systems, AI-native tooling, technical storytelling
Working style
prototype quickly, explain clearly, keep the hard parts honest
Best fit
teams that want product taste and technical depth in the same person