Gas Town Emergency User Manual

A user manual for software its author was still telling people not to use. Less than two weeks after launch, Gas Town had fifty contributors, over a hundred merged PRs, and 44,000 new lines of code no human had read, with early adopters "cheering drunkenly on LinkedIn" because it drained their bank accounts and did ten projects overnight. So Steve quit repeating the warnings and wrote down how he actually drives the thing. The joke underneath is recursive: the way he keeps up with the community's PR flood is by aiming Gas Town at its own pull requests. There's plenty of period flavor along the way, including a week-long murder spree among the town's daemons that played out "like a game of Clue," crew rosters drifting from Jane Austen toward Lord of the Rings, and standing advice to learn one new tmux keybinding every day.

Read the specific commands and crew counts as a snapshot: Steve concedes mid-essay that his workflows "change just about every week," and the version being stabilized here is 0.3.0. The advice that kept is the operating posture — never watch an agent work, and when one finishes, stop everything and read what it has to say, because that reading is the actual job now. The essay describes the payoff twice within a page, first as seeing "where all your slot machines landed," then as feeling like Jeff Bezos taking results from his team one at a time. Both comparisons are accurate, and the distance between them is a fair picture of what this kind of engineering has become.