Author here. I transcribed 400 old driving-video monologues (8 years' worth) into a queryable AI archive for $16.64 in Google API calls. This essay is about what I learned — and why I think "compounding taste" is a harder AI problem than compounding output.
If you’re using AI tools now, congratulations, you’re early. If you use them and don’t give up on them, congratulations, you’re going to have a ridiculous, potentially insurmountable advantage in output moving forward compared to AI “doomers”.
We talk about vibe coding doomers and analogous technological revolutions. We are factory farming code now.
not to spoil, but in the article I talk about vibe coding migration opportunities off of platforms like lovable, replit, n8n, etc and onto real cloud providers as an example.
thank you for the reference! I'm going to borrow the "outside in TDD" and see how well it works for my agents. they seem to do regular TDD well, but adding more structure to TDD seems like it would work even better.
Where I believe Agents will fit into the software development workflow, and why process is more important than ever for getting the most out of Claude and others.
Vibe Coding is a new skill, and everyone (including very senior people) is starting from scratch. We should give ourselves room to make mistakes and figure this thing out as a spectrum of skill, instead of a binary "it does or it doesn't work".
This post is half motivational / half beginner user guide.
It's waaaay shorter (and therefore less detailed) than Steve Yegge's original post, but I think it's got the bare minimum to get up and running on Gas Town.
I'm sure we're just working with the same tools thinking through the same ideas. Just curious if you've seen my newsletter/channel @enterprisevibecode https://www.enterprisevibecode.com/p/let-it-rip