Ship small, ship often
Long-lived branches are where projects go to die. I prefer a steady cadence of small, reviewable, revertable changes with the safety net to prove it.
3+ years of shipping for startups and studios — with a bias for systems that stay debuggable long after the launch dopamine fades.
I'm a full-stack developer who cares about the craft — clean architecture, honest performance budgets, and interfaces that feel considered down to the focus ring.
My happy place is the seam between design and engineering: shipping design systems, building product surfaces, and wiring the boring-but-critical plumbing — validation, caching, observability — that keeps products alive in production.
// currently building things that make the web feel less like homework and more like craft.
Long-lived branches are where projects go to die. I prefer a steady cadence of small, reviewable, revertable changes with the safety net to prove it.
A strict type system is a contract the compiler enforces on every save. Docs drift; types don't. I write code so the next reader — usually future me — can delete confidently.
Every 100ms of latency is a design decision someone made. I treat budgets like acceptance criteria, not aspirations, and I profile before I opine.
Keyboard paths, focus rings, contrast, semantics — baked in from the first commit, not sprinkled on before the audit. The web is for everyone or it's for no one.
$ tree ~/skills --dirsfirst
skills/
languages/
frontend/
backend/
ops & tools/
0 dependencies on things I can't debug
+ the boring-but-vital: a11y auditing · CI pipelines · code review · technical writing