This is a reply to twonines’ “What the Factory Forgets”. The post describes a factory: deterministic orchestration at the top, ephemeral AI at the leaves. The agents are caged and interchangeable; each one is spun up to produce a deterministic artifact, and then it is gone.
Disclaimer: The following text is an AI-generated summary of the design decisions and evolution of the Google Health data pipeline built with Swamp and Claude.
Companion to “Reading the board from the stands”. The short essay is about what it did to me. This is the working-out: three value chains at three altitudes — the maps and my thoughts.
Last post I built a cage — a Firecracker microVM to hold an agent I had let off the leash. This post is about what I put in it, and why the thing I put in it is a state machine and not a swarm.
Two of Simon Wardley’s predictions have sat on my map for years: that serverless was the next evolution of devops, and that conversational programming was the one after it.
I meant to buy a flat in my second year here. Then life had other plans. After a hard stretch I will not lay out in full — climbing out of something, mostly — came a year of just making things stable again, and then a year given over to the language.
The first night I got access to move.nl I spent four hours reading apartment listings and went to bed at one in the morning. I built a tool to watch the market so I do not have to.
Disclaimer: AI-generated setup guide for the JSCAD CAD pipeline. Tested on macOS, April 2026. What You Get A working pipeline: describe an object in plain text → Claude Code generates a JSCAD script → Swamp renders to STL → validator checks the geometry.
Disclaimer: The following text is an AI-generated summary of the design decisions and evolution of the JSCAD CAD generation system built with Swamp and Claude.
Disclaimer: The following text is an AI-generated log and summary of a session deploying Cozystack on a Talos cluster. All work was done in a background manner by claude-code and Swamp, and I only had to approve some steps here and there and add a hint about the ISO boot order issue.
Disclaimer: The following text is an AI-generated log and summary of a 10-hour attempt by claude-code and Swamp to virtualize macOS Tiger 10.4. Previously I had no experience running mac os in VM, nor did a I read guides, during the run I had to point claude to guides and reasonable attempts
I’ll never forget that feeling—ingesting millions of metrics into a tool like Grafana or Honeycomb for the first time. Before that, I was blind. I was guessing.
A recent post from System Initiative, “AI is an Amplifier, Why Engineers Need Better Foundations,” got me thinking about our industry workflow. You wonder why I love what they’re building?
The Genesis Engine: A Manifesto for the AI-Driven Development Lifecycle Introduction: The Old World Is Dead Saturday evening, September 20, 2025. I’m thinking about how we build.
A video from another era—2013, suddenly found me. Bryan Cantrill talking with the unshakeable confidence of someone who hasn’t yet lived through the next decade.
Recently I stumbled upon that talk https://youtu.be/3jJ1GhGkLY0 about reinventing k8s by removing unneeded docker images, and that lead to intresting consequience - They were able to create Modal an GPU serverless platform.
In thouse turbulent times it feels like another tectonic shift is happening on a devops landscape, so I’m wondering what would future hold and what will be important, like was important more than 10 years ago when devops established itself.
I was asked by a friend to advise him a devops roadmap, all the ones that I found on internet were incomplete or i just didnt like them, so after few months of thinking about that topic, and todays nudge in chat from another soon-to-be devops about roadmap.