这是一篇保留的示例内容，用来占位和验证排版。你后续可以直接替换为自己的正文。
evergreen
Gas Town’s Agent Patterns, Design Bottlenecks, and Vibecoding at Scale
On agent orchestration patterns, why design and critical thinking are the new bottlenecks, and whether we should let go of looking at code
Planted 5 months ago
Mentions around the web
this post by
Looks like your article hit HN ->
thanks for the amazing article btw
well that was quick
Article was excellent. Thank you
Loved the post. Your site though, its gorgeous.
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 em
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 ab
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
If we could orchestrate a collective ovation to this from the students in my lab over Bluesky we would do so. Thank you for fantastic writing and adding another weekly must-read site to my current AI folio.
What did you use to create the designs?
I'm very curious about this. To me the most interesting feature is the possibility of tuning with LoRA etc. Also a very gnarly data integration challenge I imagine.
Small tuned models for agents can unlock completely new user demographics than rich devs with unlimited tokens
Wow this is very good
“How close should the code be?” resonates so strongly as the design question to ask.
I've been wondering about it over a project's lifetime too -- if my code is 100% abstracted away, what happens the first time I need to dive in to diagnose and debug, with only abstract understa
following over this post. god your site's design is so pleasant. thanks!
enjoyed reading this post, thanks for writing it
“I expect companies would happily pay around the $1-3k/month mark for a sane, understandable, higher quality, and lower waste version of Gas Town”
I think you’re right but that number could easily be $10/mo and up. Pretty common for a co to spend $120k/yr on some rando software
Your diagrams rock. Chart crimes should punishable by teaching a den of polecats how to do the floss.
Also so much this ->
Thank you! I try. I really enjoy Svelte so the admiration is mutual
If you attempted to read the Gas Town article when it came out but struggled to put the sprawling cast of post-apocalyptic Hollywood movie characters together in your head into a working future vision of software development, I wrote this for you.
There are good things under the
just want to say I really enjoy your writing style (and your clarity of thought)
I love the term "agentically conversative IDE user".
And I am unreasonably proud of making all the diagrams in this responsive on mobile.
With no help from Claude. Lovingly hand-crafted only because agents are shit at visual explanations and graphic design. I am still useful for a while yet.