<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Peter Cresswell</title><link>https://petercresswell.com/tags/software/</link><description>Recent content in Software on Peter Cresswell</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://petercresswell.com/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Immobots, 25 Years Later</title><link>https://petercresswell.com/post/2026-10-01-immobots-and-ai-software-factories/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://petercresswell.com/post/2026-10-01-immobots-and-ai-software-factories/</guid><description>&lt;p&gt;Almost 25 years ago I read an article on immobots in MIT Technology Review. It stuck: &lt;a href="https://www.technologyreview.com/2002/12/01/275295/immobots-take-control/"&gt;Immobots Take Control&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I was a fresh grad at Husky Injection Molding Systems, assigned to improve self-diagnostics on injection moulding machines and their robots. It was a lovely problem. It got me thinking about monitoring systems for errors — and, more importantly, about what an error is. An immobot doesn&amp;rsquo;t watch a machine from the outside. It carries a model of the machine, compares that model to what the machine is doing, and reasons through the delta. The error is the drift — the gap between what ought to be happening and what is. That reframing has stayed with me for 25 years.&lt;/p&gt;</description></item></channel></rss>