Loose on
the ball.
I'm Leithon, a senior software engineer. Fourteen years in, and the part that still holds my attention is the point where a product stops feeling like software you have to operate and starts feeling obvious. Most of the work that gets you there is unglamorous. I like it anyway.
FRONT-END LEANING · REMOTE-FIRST
Five clubs across fourteen years, starting out in goal and working forward, plus the player wearing the shirts. Pick a number and read that report.
Hims & Hers
A consumer health product used by millions, with a blog doing serious acquisition work on top of an ageing stack. The traffic had taken years to earn, so every change carried real downside. Nothing could move without evidence behind it.
I owned the migration to Next.js and led it from the first spike to the last template, alongside large TypeScript refactors and GraphQL work in production. Officially a senior IC. Unofficially the person other teams came to when something needed a decision, on groups that ranged from four people to twenty.
The three things teams keep hiring me to do, whatever the job title happens to say.
Rendering strategy, performance budgets, Core Web Vitals. If I tell you something got faster, I can show you the trace that says so. Numbers hold up in a room where adjectives do not.
Primitives and tokens a team actually adopts, rather than quietly works around. The site you are reading is the proof: every page here is assembled from six components and one token file.
The transition that settles instead of lurching. The empty state nobody put in the ticket. I read the design file, ask about the spacing, and fix it before it ships.
Hiring, collaborating, or just want to argue about easing curves? All of it is welcome. I read and answer my own email.