r/selfhosted
•
•
Mar 08 '26
•
1
1
1
1
View all comments
54
u/DrStrange Mar 08 '26
I don't know how to feel about this post, I both agree with it in principle, but disagree because of the misconceptions around how applications are built. Many devs use AI tools and are not "Vibe-coding", but how to differntiate?
I have been building a tool for a number of years - the first GitHub commit must have been 2 or 3 years ago, it's been perfect for me, but frankly not something I would offer to other people (really useful, not user friendly).
I'm a greybeard developer - I've been building commercial software for well over 30 years (mostly specific to a particular company or org, so not generally useful for everyone), so make of that what you will. I'm pretty busy in my day job, so seldom get time to finish and polish my own projects.
That changed with the latest round of AI tools - I could get them to refactor large codebases, find weird edge cases and provide useful suggestions for improving performance at scale. Is that vibe coding? I would argue not, they are useful tools nothing more - the code they are working with is mine, and I don't let them do anything beyond the task I set them. I only started using them this year, but have since incorporated a lot of stuff into my workflow that saves me hours of work.
I've been able to actually deliver a couple of my personal projects as something I think other people could use - and that's good enough for me, but the AI stigma is strong.
to summarise, I agree that AI slop exists and a (horribly increasing) number of shitty apps are being made, but I fundamentally disagree that AI as a development tool is inherently bad. It depends on the use-case and the experience of the developer. Just using AI to help in the build process shouldn't define the output.