Post

I have Gas Town derangement syndrome and spent the last few weeks writing thousands of words on agent orchestration patterns; how they shift our bottlenecks and force us to ask whether and when we should stop looking at code maggieappleton.com/gastown

maggieappleton.comGas Town’s Agent Patterns, Design Bottlenecks, and Vibecoding at ScaleOn agent orchestration patterns, why design and critical thinking are the new bottlenecks, and whether we should let go of looking at code

Nicely written. I messed with it and fed it a Wiggun shaped problem (make this react stuff into Sveltekit and here’s how you check each component). It never quite exhausted my max account but also couldn’t parallelize beyond about 5 polecats (so like 7 agents total). I tmuxed into refinery a lot.

The biggest thing about UX work is that the robots can see some stuff but not enough. So I’d have refinery check for as much validation as it could, but then I’d have it run a container so I could see it too and raise a bunch of new beads to fix all the stuff it couldn’t sense about clarity.

0 reposts0 likes

My main take-away is that human language and tmux character injection are both bad ways to do most of these coordinations but Claude code doesn’t have machine-based alternatives. I tried to enable the OpenTelemetry logs to replace tmux scraping but it’s insufficient. Doesn’t emit the right stuff.