Self-Host Weekly (7 August 2026)

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.

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.

I don’t think you’re overexaggerating the potential backlash at all; especially on Lemmy. When I read that blurb at the top I was thinking “Bold move, Cotton…”. If you told me you get death threats over it, I wouldn’t be at all surprised.

I’ve vibecoded a number of apps that I haven’t released for about the same reasons you describe. What I have put out have been little helpers with miniscule surface area. But the bigger ones I’ve built and am improving have been tailored to my needs (or for our group) and help immensely. At one time I could have coded them myself (maybe), but I never would have gotten around to it.

What pisses me off the most is when people come down on a FOSS maintainer that uses it to keep up with bugs and security fixes because nobody can be arsed to spend any time helping them, instead they’d rather sit on the internet and criticize other people’s methods of coping with overload.