Live data from Hacker News

Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

maggieappleton.com

201–210 of 466 posts

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#201
post #61
post #27

Earlier quoted context omitted.

This is also my experience. Everything I’ve ever tried to vibe code has ended up with off-by-one errors, logic errors, repeated instances of incorrect assumptions etc. Sometimes they appear to work at first, but, still, they have errors like this in them that are often immediately obvious on code review and would definitely show up in anything more than very light real world use. They _can_ usually be manually tidied…

Yeah, it sounds like "you're holding it wrong" Like, why are you manually tidying and fixing things? The first pass is never perfect. Maybe the functionality is there but the code is spaghetti or untestable. Have another agent review and feed that review back into the original agent that built out the code. Keep iterating like that. My usual workflow: Agent 1 - Build feature Agent 2 - Review these parts of the code,…

I haven’t used multi-agent set up yet but it’s intriguing.

Are you using Claude Code? How do you run the agents and make them speak?

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#202

Earlier quoted context omitted.

Is this confirmed true? Yegge has a very very long history of writing absurdly long posts / rants.

Back in the day they used to be coherent.

Not much more than his recent posts, no.

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#203
post #174
post #171

Am I wrong that this entire approach to agent design patterns is based on the assumption that agents are slow? Which yeah, is very true in January 2026, but we’ve seen that inference gets faster over time. When an agent can complete most tasks in 1 minute, or 1 second, parallel agents seem like the wrong direction. It’s not clear how this would be any better than a single Claude Code session (as “orchestrator”) runni…

It's likely then that you are thinking too small. Sure for one off tasks and small implementations, a single prompt might save you 20-30 mins. But when you're building an entire library/service/software in 3 days that normally would have taken you by hand 30 days. Then the real limitation comes down to how fast you can get your design into a structured format. As this article describes.

Agree that planning time is the bottleneck, but

> 3 days

still seems slow! I’m saying what happens in 2028 when your entire project is 5-10 minutes of total agent runtime - time actually spent writing code and implementing your plan? Trying to parallelize 10m of work with a “town” of agents seems like unnecessary complexity.

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#204

Earlier 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…

Keep in mind that Steve has LLMs write his posts on that blog. Things said there may not reflect his actual thoughts on the subject(s) at hand.

I've been reading Steve's posts for quite literally a decade now and I don't think his new posts are so meaningfully different from the old ones that he's not at the wheel any more. Besides, his twitter posts often double down on what he's writing in the blog, and it's doubtful he's not writing those.

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#205
post #81

I don't get the widespread hatred of Gas Town. If you read Steve's writeup, it's clear that this is a big fun experiment. It pushes and crosses boundaries, it is a mixture of technology and art, it is provocative. It takes stochastic neural nets and mashes them together in bizarre ways to see if anything coherent comes out the other end. And the reaction is a bunch of Very Serious Engineers who cross their arms and h…

Perhaps it was his followup post about how people are lining up to throw millions of VC dollars at his bizarre whimsical fever dream that disturbs people? I’m all for arts funding, but…

Isn't the point that he refused them? VCs can be dumb (see the crypto hype, even the recent inflated AI raises) so I wouldn't put too much stock in what they think is valuable.

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#207
post #133

Earlier quoted context omitted.

> I don't get the widespread hatred of Gas Town. Fear over what it means if it works.

I work in a typical web app company which does accounting/banking etc. A couple of days ago I was sitting in a meeting of 10-15 devs, discussing our AI agents. People were raising issues and brainstorming ways around the problems with AI. How to make the AI better. Our devs were occupied doing AI things, not accounting/banking things. If the time savings were as promised, we should have been 3 devs (with the remainin…

Isn't that fun though? We get paid to fuck around. People say AI is putting devs out of jobs, I say we're getting paid to play with them and see if there's any value there. This is no different from the dev tools boom of the ZIRP era: I remember having several sprints worth of work just integrating the latest dev tool whose sales team won our execs over.

This is only partly tongue in cheek :P

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#208

Earlier quoted context omitted.

Yeah where he probably Burns like a million dollars of money. Just for fun!

He's paying $600 a month for 3x Claude Max subs. It's in his article.

…and now funded by a $GAS crypto coin on the BAGS platform so it even pays for itself!

https://steve-yegge.medium.com/bags-and-the-creator-economy-...

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#209

I don't get the widespread hatred of Gas Town. If you read Steve's writeup, it's clear that this is a big fun experiment. It pushes and crosses boundaries, it is a mixture of technology and art, it is provocative. It takes stochastic neural nets and mashes them together in bizarre ways to see if anything coherent comes out the other end. And the reaction is a bunch of Very Serious Engineers who cross their arms and h…

Links to Steve's writeup for Gas Town for those who don't have them yet:

[Medium post]: https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16d...

[HN Discussion]: https://news.ycombinator.com/item?id=46458936

Re: Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

#210

Earlier quoted context omitted.

So I’m probably in a similar spot - I mostly prompt-and-check, unless it’s a throwaway script or something, and even then I give it a quick glance. One thing that stands out in your steps and that I’ve noticed myself- yeah, by prompt 10, it starts to suck. If it ever hits “compaction” then that’s beyond the point of return. I still find myself slipping into this trap sometimes because I’m just in the flow of getting…

I will check out Ralph (thank you for that link!). > Another way is “Write out what we did to PROGRESS.md” - then start new session - then “Read @PROGRESS.md and do X” I agree on small context and if I hit "compacting" I've normally gone too far. I'm a huge fan of `/clear`-ing regularly or `/compact ` and I've also tried "TODO.md"-style tracking. I'm conflicted on TODO.md-style tracking because in practice I've had a…

I hate TODO.mds too. If I ever have to use one, I'll keep track of it manually, and split the work myself into chunks of the size I believe CC/codex can handle. TODO.md is a recipe for failure because you'll quickly have more code than you can review and nothing to trust that it was executed well.
Post reply on HN