The loom is basically code you can touch

I keep coming back to the loom as a better programming metaphor than another boxes-and-arrows diagram.

The warp threads hold state. Treadles are inputs. The shafts decide which threads are active. The shuttle carries material through the system. Repetition becomes structure you can literally touch.

The part I like most is the undo model. Software lets me hit Ctrl+Z and pretend a decision never happened. A loom is less diplomatic. If the mistake is ten picks back, the cloth asks you to travel physically backward through the decisions that produced it.

A loom is a debugger with consequences.

That connection is becoming part of how Sticatto talks about software: less glowing circuit-board imagery, more tension, structure, crossings, drafts, mistakes, and repair.