Logdyco

Gas Town’s Agent Patterns, Design Bottlenecks, and Vibecoding at Scale

À propos de Gas Town, un outil d'orchestration d'agents:

I certainly feel this friction in both my own professional work and personal projects. My development velocity is far slower than Yegge since I only wrangle a few agents at a time and keep my eyes and hands on the code. But the build time is rarely what holds me up. It is always the design; how should we architect this? What should this feel like? How should this look? Is that transition subtle enough? How composable should this be? Is this the right metaphor?

Complètement d'accord. Personnellement, sur les projets "vibe-codés" (entendre, je m'éloigne beaucoup du code) je ne souffre pas de ce "ralentissement", j'aime passer du temps sur ces idées, choisir ce que je met dans le produit, reprendre les commandes sur une partie intéressante.

This feels like one of the most critical, emerging footguns of liberally hands-off agentic development. You can move so fast you never stop to think. It is so easy to prompt, you don’t fully consider what you’re building at each step of the process. It is only once you are hip-deep in poor architectural decisions, inscrutable bugs, and a fuzzy memory of what you set out to do, do you realise you have burned a billion tokens in exchange for a pile of hot trash.

Mon intuition initiale à propos du vibe-coding, des patrons et commerciaux qui veulent qu'on s'éloigne du code ou développer les outils eux-même. Yegge, l'auteur de Gas Town est peut être un peu extrême, donc l'issue finale arrive vite. Mais j'ai du mal à me dire que tout projet sans conception et connaissance des enjeux sous-jacents est voué au même destin.

Gas Town’s hierarchical approach solves both a coordination and attention problem. Without it, you are the one assigning tasks to dozens individual agents, checking who’s stuck, who’s idle, and who’s waiting on work from someone else. With the Mayor as your single interface, that overhead disappears. You can continuously talk to the Mayor without interrupting any agents or getting in the way, or having to think much about which one is doing what. This is less cognitive overhead than constantly switching tabs between Claudes.

Si le développement prend cette direction, on va tous devenir des CTO à diriger des sortes d'usine à logiciel. Il faudra viser juste dès l'idée et les premiers prompts au risque d'avoir financé un produit à jeter dès la sortie d'usine.

Gas Town’s solution to this is make each agent session disposable by design.

Ce n'est pas nouveau. Les Ralph Loops et autres boucles agentiques avaient le même prémisse. Gas Town semble hériter beaucoup d'idées directement des autres candidats qui ne sont plus assez nouveaux pour qu'on continue d'en parler 3 mois plus tard.

“Should developers still look at code?” will become one of the most divisive and heated debates over the coming years. You might be offended by the question, and find it absurd anyone is asking. But it’s a sincere question and the answer will change faster than you think.

J'espère que oui, le code, l'archi, les algorithmes, les concepts, les systèmes. La créativité n'est pas qu'imaginer des produits et leur rentabilité.

I’m already seeing people divide along moralistic, personal identity lines as they try to answer it. Some declare themselves purist, AI sceptic, Real Developers who check every diff and hand-adjust specific lines, sneering at anyone reckless enough to let agents run free.

Sans parler de ceux qui disent ça et produisent 5 ans de dev en 1 mois !

How far away you step from the syntax shifts based on what you’re building, who you’re building with, and what happens when things go wrong.

Un peu de déculpabilisation.

Gas Town sounds fun if you are accountable to nobody: not for code quality, design coherence or inferencing costs. The rest of us are accountable for at least the first two and even in corporate scenarios where there is a blank check for tokens, that can’t last. So the bottleneck is going to be how fast humans can review code and agree to take responsibility for it.

  • qcnguy, comment on Hacker News post about Gas Town

Given all these “it depends” considerations, I’m currently in the code-must-be-close camp for most serious work done by professional developers. But I expect I’ll shift to the code-at-a-distance camp over the next year or two as the harnesses and tools we wrap around these agents mature.

Il suffit de regarder comment nos pratiques ont évolué ces derniers 6 à 8 mois.

Super post, belles illustrations, décidément l'équipe de Github Next sait soigner les apparences et le contenu.

Extraits cités issus de ce lien visité le , crédits: Maggie Appleton