I made a new CLI tool to make switching between jj workspaces a bit less annoying. Or, at least, I published it: I haven’t written a single line of code, other than a little CSS when tweaking the webpage. My process was to iteratively prompt Claude Code until I had something that worked the way I want. Because I was at work, and this is a side project, I babied the coding agent much less than I typically do, instead just checking in every ten minutes or so to rebuild, poke around to see what worked and what needed to change, and reprompt.
posts
I’m sure we’ll all get bored of doing this soon, but:
Self-adjusting computation is a technique for breaking up a complex, expensive-to-execute task into a graph of smaller subtasks which can be computed incrementally. The advantage to this is that re-running the task after making changes will be much faster than running it from scratch, because only the part of the graph that has changed, and any nodes that depend on it, will actually be re-executed. Right now, for whatever reason, there’s a sudden vogue for reactive state management in JavaScript developer circles—this topic touches directly on SAC, so I thought I’d go over how these systems can be built in practice.
I’ve been leaning on CSS custom properties more and more at work. They’ve been around for years now, and I think they’re a little underused and underappreciated. Unlike other newish features in CSS, like grid, they don’t really unlock new ways of styling a page that weren’t possible before. Instead, they’re a great organisational tool for the programmer, which is powerful in its own way.