It’s always more work than it looks. You can get to mostly usable tools quickly if your request isn’t too difficult, but every time I use them I run into another thing that needs to be fixed, changed, clarified, or cleaned up.
It’s fun at first, but over time you realize you’re spending more time building the tools than using the tools to build the thing you originally wanted to work on.
I think personal software is best for highly specific tools or for things you need to use repeatedly for a very long time.
For something like a SketchUp competitor, I wouldn’t want to try to maintain my own. The number of edge cases and features is bigger than you imagine up front, and the vibecoded version that might appear a few hours after your prompt is going to be very far from the version you want to use.
The vibecoded apps all rely on an army of users exploring the program and reporting all the bugs and edge cases. You don’t want to be doing that on your own.
it seems like the open-source space is losing some aspects of collaboration. people used to search for already existing projects on some git-hosters, maybe fork them or put effort into the existing thing. now half a dozen people each run their own race using AI, each solution misses 30% of the features and has x-amounts of bugs.
work together ffs :( i mean, 20 people can use AI to vibecode the same project, why does everyone now feel the need to do everything solo. (because they want to be the prolific founder and cool dude who did the most in the project* instead of being one of many contributors, i assume...)
*or rather, their AI.
I'm not too sure what the future here looks like and if this is even a problem, but things certainly are changing. These days submitting a well written bug report or feature suggestion, or validating existing reports is more useful than sending a PR.
Right, and that's something I already argued for since the very beginning of GenAI, namely that suddenly being very costly, economically and ecologically, is not that bad if you build upon what exists and collaborate on progress.
... except that's exactly WHY vibecoded project exist : they do NOT have to give a shit with existing codebase and agree on weird rules. They just start from "scratch". In fact I'm convinced there is the Ikea effect at play, namely that the PM of the vibe coded project is emotionally attached, even proud, of the result they think they provided somehow, despite them not actually doing it. Obviously for-profit GenAI companies have a big incentive to maximize token use and will never promote workflows and tool that minimize the one thing they monetize.
So even though I agree in theory, in practice I think there is little to no overlap.
I have lot of tools that work for me.
When externalities break them, it's usually one prompt to fix them.
To be fair neither is quite as complex as a whole 3D modeller.
> To be fair neither is quite as complex as a whole 3D modeller.
Once you cross a certain complexity in your project, it becomes quite work intensive even using AI to do the coding. All the back and forth and cleaning up, exploring ideas and starting from scratch again takes time and effort and maybe most importantly, extensive human thinking. Just to clarify, I am not against AI and use it extensively myself. But vieb-coding all your tools is just not really a feasable idea for most (time/token-cost constraint) if you tools are of a certain complexity.
But you could easily vibe code, e.g. an H.265 decoder, even though it is super complex.
AI can get the implementation done just fine but in my experience it needs guidance because it can't guess what features and details I want / don't want.
The difference to "before" is that it's now possible at all for me to get personal projects to a working state but in sum they still require a few hours every now and then supervising.
My personal projects matter a lot. For some of them I am trusting my private data in the code, so I need to hold it to a high security and privacy standard. For others, I have hundreds or thousands of users (game mods, helper tools for hobbies, etc.), and I don't want to ship low quality to them.
If it doesn’t matter then do what you want. By definition, it doesn’t matter.
Some of us actually use these tools, so it does matter. You do have to consider things when it matters.
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.
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.