THE JOURNAL.

//What's here#

Seven entries, each on something specific I've had to work out properly. Scroll-driven animation without the usual state bugs. Shaders for people who write application code. Render budgets as a design constraint rather than a QA step. Motion that carries meaning. Accessible motion done as a design problem. State that survives a bad network. And typography on the web, which I keep relearning.

//Why write at all#

Because I don't understand something until I've had to explain it in order. Several times I've started an entry confident about a technique and discovered halfway through that my explanation had a hole in it — which sent me back to the code to find that the implementation had the same hole. Writing is the cheapest code review available.

There's a second reason, less noble: I forget things. A note written while the problem was fresh is worth considerably more than a memory of having solved it once. Roughly a third of these entries exist because I needed the information again and couldn't find it anywhere in my own head.

//What you won't find#

Framework comparisons, hot takes on tooling, or posts about how to get into the industry. There's plenty of that and I have nothing to add. These are narrow, technical and occasionally opinionated about timing values.