Notes onbuilding with AI.
Field notes on AI transformation, engineering leadership and the trends I'm testing in the real world.
Can you prove how your software was built?
From 11 September 2026 you have 24 hours to report an actively exploited vulnerability. Meanwhile a quarter of production code is written by machines and nobody can say who decided what. A bill of materials tells you what is in your software. Nothing tells you why.
How to set up OpenClaw and 15 jobs it can take off your team
OpenClaw runs on your own machine and actually does things instead of answering questions about them. Setup takes about ten minutes. Here is the plain-language version, the settings that keep it out of trouble, and three real jobs each for engineering, the CEO, support, sales and procurement.
Beyond copilots: designing AI workflows that stick
You bought everyone a license a year ago and no number moved. That is not an adoption problem. You sped up a step that was never the expensive part, and here is what changing the actual workflow looks like.
You do not have a timezone problem
Engineering in Armenia and India, QA in Sri Lanka, product in Bengaluru, me in Luxembourg. A one line fix could take three days. Then I did the arithmetic on the clocks and found the sun was responsible for almost none of it.
The AI Act got delayed. The part that applies to you did not
Brussels moved two AI Act deadlines to 2027 and 2028. The rule covering your support agent, your AI outreach and your generated newsletter started applying on August 2. Two questions tell you if you are caught.
What breaks when your team ships 4 times more code
Everyone is optimizing the part that writes code. Almost nobody has resized the system that consumes it. Here is what actually failed when our throughput went up 4x, in the order it failed, with the arithmetic that explains why.
What to measure when the machine writes the code
A harness without KPIs is a fast way to be confidently wrong. Here is the metric set that actually explains whether agentic development is working, how to instrument it with OpenTelemetry, and what the same setup looks like at 8 engineers and at 800.
From CTO to transformation partner
The four-year CTO tenure was built around how long it took to build things. Agents just broke that clock. The job that is left is not running the org that builds, it is changing how the org works, permanently.
What I'm watching in 2026
If you can act on it this quarter, it is not a trend, it is news. Five clocks are already running that will land on ordinary European companies between 2027 and 2030, and most of them have nothing to do with which model is on top this month.
I write this myself, fortnightly. Unsubscribe anytime.