Weeknotes 2026 week 10

Here are my weeknotes for the last week, while I'm still writing up some more focused posts on some specific topics - like the experience of putting everything in a monorepo to create this site, and more notes on Claude and Agentic coding in general, and its impact on the world of software. But for now, here's what I've been up to.

What did I do?

• New site design. The old site was a bit of a mess and was simply reusing odoc's default default styling. I've also rearranged the content a bit to make it more navigable and cohesive.

  
  

• TESSERA in the browser is a hot topic right now, so I've applied the work I've been doing with x-ocaml, js_top_worker and odoc plugins to make a TESSERA notebook that's based on the example notebook.

  
• I was interested in whether we'll be able to do inference in reasonable time using these notebooks. ONNX has a web version of its runtime, so I got Claude to make some bindings, and checked it was working by doing a sentiment analysis notebook. This is working nicely, so the next step is to do something a bit more useful.
• The docs CI was again causing problems. This time it had decided that it had never built anything, and therefore needed to rebuilt the entire world. However, despite being set up as a custom dedicated runner, all its jobs were queued waiting to start. It turned out that the runner paused itself when the docker partition reached 70%. This was a little surprising on two counts - firstly we don't actually use docker for running the jobs, we use obuilder, which doesn't share space with docker. Secondly, with that in mind, how did it get to 70%? It turned out to be the job logs - including 250 gigs of older logs from a previous instance. Simply blowing those away caused everything to restart and so it's now live again.
• I met up with Andrés C. Zúñiga-González to have a chat about how he's using interactive maps and notebooks. He pointed me at his blog, some of which which is using quarto, which he rates very highly. An example of quarto output.
• Our group seminar this week was Tom Bearpark who talked about his proposed 'Carbon at Risk' measure in order to compare diverse ways of removing carbon from the atomsphere to help with the carbon removal market.

What's next?

• More writing before more coding, I think.