Side Projects
Building things to understand them.
Side experiments where I write the code, own the infrastructure, and learn what I couldn't from Figma alone.
What is Vibe Coding?
Vibe coding is low-ceremony building — no product spec, no stakeholder reviews, no design-dev handoff. Just an idea, a rough plan, and a browser. The goal is learning through shipping, not shipping through learning.
Current experiments
Retention Loop Simulator
LiveA playground for modeling D1–D30 user retention curves. Tweak cohort size, churn rate, and reward frequency to see where lifecycles break.
IA Audit Tool
In ProgressPaste a sitemap or nav structure and get an instant structural analysis — depth score, orphan nodes, and cognitive load estimate.
Decision Frame Generator
PrototypeConverts a messy product brief into a structured decision doc with options, tradeoffs, and a recommended frame — for faster stakeholder alignment.
Friction Audit Chrome Extension
ConceptHighlights UX friction points on any web page — excessive form fields, confusing CTAs, missing affordances — using heuristic rules.
Perspective
Why building informs design
Constraints sharpen decisions.
When I'm the designer and developer, there's no room to design things that can't be built. Scope negotiations happen in my head, not in Jira.
Shipping beats speccing.
A working prototype reveals more about a design problem than 40 annotated Figma frames. Vibe coding forces me to confront the real thing.
Engineering literacy is a design superpower.
Understanding component architecture, state management, and performance tradeoffs makes me a better systems designer — not just a better collaborator.