In my own words

Early curiosity

I grew up in City, where the best afternoons were spent taking things apart and trying to put them back together. “View source” was my teacher. I learned that a small page on the web can help someone you’ll never meet.

What I care about

My compass is simple: clarity first, then power. I prefer tools and products that respect attention. I believe accessibility isn’t an add-on; it’s part of the craft. Performance is part of that, too — a fast interface is a kind one.

Good interfaces make hard things feel understandable — not trivial, but graspable.

I try to write code as a letter to the next person who reads it. Names that explain themselves; components that do one thing well; comments that tell you why, not what.

Formative moments

There were turning points: the first time a tutorial I wrote helped strangers fix a problem; the first talk where I shared how tiny accessibility tweaks changed a team’s confidence; the first project where design, writing, and code finally felt like one language.

• “View source” summer. Learned by breaking and mending.
• First helpful post. Dozens of thank-you emails kept me writing.
• Local meetup talk. Small a11y wins, big impact.

Now

I’m exploring micro-interactions, design tokens, and kinder defaults. Outside the screen: coffee, long walks, and a camera that teaches me how to see.

How I work

Start with words. Shape the structure. Layer in interaction. Measure what matters. Leave space for the next person. When the work’s good, it gets quieter.