01 — About

Engineer by trade.
Front-end by instinct.

I'm Leithon, a senior software engineer who's been building for the web for fourteen years. I've spent most of that time fascinated by the part where engineering and design meet: how something works, how it feels, and all the small decisions that make the difference.

I didn't always plan on becoming an engineer. For a long time, I wanted to be an architect. I loved the drafting, the precision, and the idea that decisions made early could quietly determine whether the finished thing worked at all.

Life took me somewhere else, but the part I was drawn to never really changed.

I still like taking something abstract and giving it structure. I still obsess over the details that are easy to dismiss until they're wrong. And I still get a particular kind of satisfaction from building something that feels inevitable once it's finished.

That's probably why I've always gravitated toward the front end.

I care about the transition that lands exactly where you expect it to. The page that's ready before you notice it loading. The component another engineer can pick up without first having to understand the mind of the person who wrote it.

A lot of my best work looks, from the outside, like nothing happened at all. No friction. No hesitation. No reason to think about the engineering underneath it.

I've made peace with that.

Away from the keyboard, you'll usually find me around the football field, and I think some of my standards come from there too. A good first touch gives you time. It creates options. Done well, something difficult can look almost obvious.

That's the feeling I'm chasing when I build interfaces.

Leithon and his daughter
MY TOUGHEST CRITIC · AND THE
REASON THE DAD JOKES LAND.
02 — How I work

Three habits that turn up in everything I ship, whether or not anybody asked for them.

01
Measure, then move

Performance work without numbers attached to it is decoration. I would rather spend an hour on a trace than a week on a hunch.

02
Design is my job too

I read the design file properly, ask why the spacing is what it is, and fix the things that were never specced before they reach anyone.

03
Leave it better

Docs that are current, primitives worth reusing, a nav that makes sense. Nobody joining after me should have to guess.

Want the short version?

Dates, outcomes, and a résumé you can download and take into a meeting.

Career →