

Working effectively in Gas Town involves committing to vibe coding. Work becomes fluid, an uncountable that you sling around freely, like slopping shiny fish into wooden barrels at the docks. Most work gets done; some work gets lost. Fish fall out of the barrel. Some escape back to sea, or get stepped on. More fish will come
Oh. Oh no.
First came Beads. In October, I told Claude in frustration to put all my work in a lightweight issue tracker. I wanted Git for it. Claude wanted SQLite. We compromised on both, and Beads was born, in about 15 minutes of mad design. These are the basic work units.
I don’t think I could come up with a better satire of vibe coding and yet here we fucking are. This comes after several pages of explaining the 3 or 4 different hacks responsible for making the agents actually do something when they start up, which I’m pretty sure could be replaced by bit of actual debugging but nope we’re vibe coding now.
Look, I’ve talked before about how I don’t have a lot of experience with software engineering, and please correct me if I’m wrong. But this doesn’t look like an engineered project. It looks like a pile of piles of random shit that he kept throwing back to Claude code until it looked like it did what he wanted.
It’s okay, he definitely wants to verify it but actually confirming that this whole disaster pile worked as intended and produced usable code apparently didn’t make the cut.
Also worth noting that in the jargon he’s created for this, a “wisp” is ephemeral rather than a proper output, so it seems like he may have pulled this solution out of the middle of a running attempt to calculate the solution and assumed that it was absolutely correct despite repeatedly saying throughout his writeup here that there’s no guarantee that any given internal step is the right answer. This guy strikes me as very good at branding but not really much else.