I've been doing this since tables were a layout tool.

I build the front of websites, and I've been doing it long enough to have watched the same argument come back around four times wearing different clothes. Frameworks arrive, promise to make layout easy, make it easy for two years, then leave. The people who understood what the browser was doing underneath moved on fine. The people who only knew the framework had to start again.

That's most of what I write about. Not because the fundamentals are noble, but because they're the only part with a good return on the time you spend learning them.

What I actually do

Architecture, day to day — currently as Technical Architect at DEPT®. Deciding how a large site holds together so that the third team to touch it doesn't have to rewrite it. Performance work, which is usually archaeology — finding out where a codebase started paying interest on a decision someone made in a hurry. And accessibility, which I've stopped arguing for on moral grounds because the practical argument wins faster: it's the same work as building it properly.

This site is separate from that. What's here is mine — the writing, the demos, the opinions — not DEPT®'s, and not a pitch for work.

Why the demos

Because I've read a hundred posts explaining CSS Grid and understood roughly none of them until I dragged something. Prose is good at why. It's bad at watch this happen. So every post that has a mechanism in it gets a thing you can break, and if I can't build the demo, that's usually a sign I don't understand the topic well enough to write about it yet.