alt Hacker NewsI was talking about AI developed tooling.
It’s amazing that you can get something usable quickly, but then every time you use the software you’re back in the AI working on your tool.
Using AI to build the tool becomes the project, replacing the project that led you to think about vibecoding a tool.
I'm coming to think that a hybrid of vibe-coding but with an existing substrate is the right way to go.
For instance in the context of this SketchUp clone that might mean using AI to generate an addon for Blender.
For some of my recent projects I'm using the community edition of Odoo to serve as that substrate because it already has an established community of modules to draw from, ten years or so of real world use, and I don't have to burn tokens generating a user account system with permissions or the data models / ORM to interface with them.
This seems to be serving me well, but we'll see. It could be that I end up in the same the tool becoming the project scenario that you describe, just a little bit later than if I had started from a blank slate.