posted in Selfhosted
Self-Host Weekly (7 August 2026)
selfh.st/weekly/2026-08-07/
selfh.stSelf-Host Weekly (7 August 2026)I'm pickin' up good (vibe)rationsposted in Selfhosted
Self-Host Weekly (7 August 2026)
selfh.st/weekly/2026-08-07/
selfh.stSelf-Host Weekly (7 August 2026)I'm pickin' up good (vibe)rationsReplying to @darcmage@lemmy.dbzer0.com
It’s cool that he vibe coded something for his specific needs but the lamenting of being unable to share it because of the fear of a backlash is a bit premature. I wonder how long he (and others like him) will be able to keep his project going when he eventually adds more features that introduce more bugs and the effort/cost of maintaining the project becomes too much. We’ve already seen that for the majority of people vibe coding stuff, the answer is relatively quickly.
I’ve found interesting projects that have been vibe coded and seem to be well-maintained but I think vibe coded projects need at least 6 months to a year of history before they replace anything critical in my stack.
Replying to @darcmage@lemmy.dbzer0.com
Hey, I’m the editor/author. I may be overexaggerating the backlash a bit, likely because I spend so much time curating content for the newsletter each week that I’m constantly exposed to the worst-of-the-worst reactions.
Replying to @eshol@lemmy.world
I think some of the problem is the term vibe coding. If I want a small app to help something specific I used to look at it and go is it worth writing it for the return most of the time I was just too busy.
Now I sit down and write up a small document outlining what I want why I want it and the outcome typically I’d use AI then to review it and give any suggestions that I may not have thought of and use that for the seed for the application.
That is the document I use with an agent to actually do the code generation. I push that to a local GIT instance and the document lives with the code and then gets iterated overtime and then I typically use the issues list to add improvements and fixes to it again iterating through the issue before I think about letting an agent do it
To me vibecoding is just putting a sentence in and hoping for the best I like a little bit more structure than that.
Again, most of this is for personal use so I don’t share it widely a few friends have access to some of the stuff I’ve written because it helps them. I only ever released one AI first project on GitHub and I probably won’t go any further than that.
Replying to @sytone@lemmy.world
I think some of the problem is the term vibe coding.
Spot on. Most engineers at companies are using LLMs nowadays but when we use it in our daily lives it becomes “vibe coded”.
I’ve started using the term agentically built or agentically driven instead.