I had been dreading today's task since the month begun, I knew I'd have to eventually make Drifblim able to survive being thrown paths interactively. The original design expected to be terminated after assembly, relying on self-modification like nobody's business it left the original assembler data in memory nearly unrecognizable after a run. The project here was to make sure that it recovers into a usable state, even after erroring.
I even went a bit overboard with the recovery pass and I made it so it's optimizing itself a bit each pass. Let's call it .. antifragile software.