| ▲ | Aurornis 2 hours ago | |||||||||||||||||||||||||||||||||||||
I have several personal tools I’ve built and maintained. 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. | ||||||||||||||||||||||||||||||||||||||
| ▲ | Gigachad 6 minutes ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||
I’ve been using the vibecoded Lightroom clone and it’s 5000 commits and around 20 releases in yet still has countless issues and missing features. I feel like it will get there eventually but the idea that you should just vibe up your own Lightroom rather than using an existing one is absurd with today’s tech. It’s still a massive amount of work even if it is way faster than ever before. 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. | ||||||||||||||||||||||||||||||||||||||
| ▲ | altmanaltman an hour ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||
Isn't the whole argument that ai-driven code will reduce the time spent building because AI can do it now? And a SketchUp competitor by defintion will not be personal software just like SketchUp is not. | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||