I make things for the web and keep notes along the way.

I'm a software engineer interested in the parts of the web that sit just beneath the surface — rendering, performance, architecture, tooling, and the small decisions that make software easier to live with.

Most of my day-to-day work is on large customer-facing web applications, particularly e-commerce systems. I spend a lot of time thinking about front-end architecture, performance, maintainability, and what actually happens between writing some code and putting it in front of real people.

I like software that feels simple because somebody took the time to deal with the complicated parts.

_{FIELD NOTE No. L–002 · CURRENT INTERESTS}

Things I keep circling back to:

architecture & rendering
front-end architecture · SSR / SSG · islands · resumability

performance
code-splitting · bundle optimization · browser performance

systems & tooling
framework internals · developer tooling · reactive systems

Current observation

The web keeps getting more capable while our abstractions keep getting heavier.
I’m interested in the places where we can remove machinery instead of adding more of it.

_{working theory — subject to revision}

_{Things I work with, reach for, or spend entirely too much time poking at.}

_{THINGS I'VE WRITTEN DOWN AND KEPT}

_{01 / PERFORMANCE}

Fast software doesn't just benchmark better. It feels better.

_{02 / ABSTRACTION}

If an abstraction mostly gives us more vocabulary to remember, I'm not convinced it helped.

_{03 / UNDERSTANDING}

Framework knowledge expires. Understanding rendering, state, networks, browsers, and software design tends to stick around.

_{04 / SHIPPING}

The awkward parts usually don't introduce themselves until somebody actually has to use it.

_{05 / OWNERSHIP}

The implementation is only part of the job.

_{observe · tinker · understand}

_{notes, experiments, essays, and observations about code, systems, and the web}