>while Yegge made lots of his own ornate, zoopmorphic [sic] diagrams of Gas Town’s architecture and workflows, they are unhelpful. Primarily because they were made entirely by Gemini’s Nano Banana. And while Nano Banana is state-of-the-art at making diagrams, generative AI systems are still really shit at making illustrative diagrams. They are very hard to decipher, filled with cluttered details, have arrows pointing…
Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
301–310 of 466 posts
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#302Earlier quoted context omitted.
I feel like it was doing what you're saying about 4-6 months ago. Especially the commenting out tests. Not always but I'd have to do more things step by step and keep the llm on track. Now though, the last 3-4 months, it's writing decent unit tests without much hand holding or refactors.
Hmm, my last experience was within the last 2 months but I'm trying not to write it off as "this sucked and will always suck", that's the #1 reason I keep testing and playing with these things, the capabilities are increasing quickly and what did/didn't work last week (especially "last model") might work this week. I'll keep testing it but that just hasn't been my experience, I sincerely hope that changes because an…
if "--no-verify" in sys.args:
println("--no-verify is not allowed, file=sys.stderr)
sys.exit(1)
and otherwise forwards to the underlying `git`Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#303If we had super-smart AI with low latency and fast enough speed, would the perceived need for / usefulness of running multiple agents evaporate? Sure you might want to start working on the prompt or user story for something else while the agent is working on the first thing, but - in my thought experiment here there wouldn't be a "while" because it'd already be done while you're moving your hand off the enter key.
(Maybe you can argue that you could then do everything with a event-driven single agent, like async for llms, if you don't mind having a single very adhd context)
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#304Earlier quoted context omitted.
> Chefs do learn the chemistry, at least enough to know why their techniques work Cooks are idiots (most are either illegal immigrants with no formal education, or substance-abusing degenerates who failed at everything else) who repeat what they're told. They think ridiculous things, like that searing a stake "seals in the juices", or that adding oil to pasta water "prevents sticking", that alcohol completely "cooks…
Cooks also repeatedly cook the exact same recipe designed by someone else over and over again. In our industry cooks are closest to the CPU executing machine code.
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#305Earlier quoted context omitted.
It isn't though. It crossed the chasm when Steve (who I would like to think is somewhat comfortable after writing a book, holding a director level position at several startups) decided to endorse an outright crypto pump and dump. When he decided to monetize the eyeballs on the project instead of anything related to the engineering. Which, of course, Steve isn't smart enough to understand (in his own words) and he rec…
Okay yeah, not great... https://steve-yegge.medium.com/bags-and-the-creator-economy-...
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#306Earlier quoted context omitted.
> If you read Steve's writeup, it's clear that this is a big fun experiment: So, Steve has the big scary "YOU WILL DIE" statements in there, but he also has this: > I went ahead and built what’s next. First I predicted it, back in March, in Revenge of the Junior Developer. I predicted someone would lash the Claude Code camels together into chariots, and that is exactly what I’ve done with Gas Town. I’ve tamed them to…
These are some very tortured interpretations you're making. - "what's next" does not mean "production quality" and is in no way mutually exclusive with "experimental". It means exactly what it says, which is that what comes next in the evolution of LLM-based coding is orchestration of numerous agents. It does not somehow mean that his orchestrator writes production-grade code and I don't really understand why one wou…
That's hilarious! You might want to add a bit more transition for the joke before the other points above, though.
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#307Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#308Earlier quoted context omitted.
After listening to Yegge's interview, I'm not sure this is accurate: https://www.youtube.com/watch?v=zuJyJP517Uw For example, he makes a comment to the effect that anyone using an IDE to look at code in 2026 is a "bad engineer."
Hyperbole is very common.
A result, hyperbole is more annoying than usual.
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#309Earlier quoted context omitted.
It's a half-joke. No need to take it that seriously or that jokingly. It's mostly only grifters and cryptocurrency scammers claiming it's amazing. I think ideas from it will probably partially inspire future, simpler systems.
stevey already made $300K from cryptocurrency grift on Gas Town. Read his blog post about it.
Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
#310Maybe Yegge’s 8 levels of automation will be more important than his Gas town.