Self-Host Weekly (7 August 2026)

Comments

• darcmage@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

  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.

  original

  • eshol@lemmy.world ⁨2⁩ ⁨days⁩ ago

    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.

    original

    • ikidd@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

      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…”.

      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.

      original

      • -> View More Comments
    • non_burglar@lemmy.world ⁨2⁩ ⁨days⁩ ago

      I appreciate tour candor, but do you understand why the backlash happens?

      original
    • curbstickle@anarchist.nexus ⁨2⁩ ⁨days⁩ ago

      Actually given that, if you have a weekly with AI as part of it, tagging [AIT] will allow people to filter it out.

      Its pretty ancillary to the newsletter itself so its not really required, but just to mention… if it were tagged, any low effort comments like “slop” or similar would then be removed. I don’t really see that on your posts in general though, so more a thought for later should it become a problem.

      original
    • darcmage@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

      That’s fair. I’m sure we have wildly different experiences around the discussion of vibe coded projects.

      original
    • sytone@lemmy.world ⁨2⁩ ⁨days⁩ ago

      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.

      original

      • -> View More Comments
  • bluGill@fedia.io ⁨2⁩ ⁨days⁩ ago

    Even hand coded projects need more than 6 months before I'll replace anything in my stacks. Too many projects start with great intention but then the founder gets bored (life gets in the way?) and they go unmaintained. Really I'm looking for projects that enough developers have got involved in that I can be confident it won't go stagnant. I could be one of those developers, but I don't have enough time to contribute to all the different projects I use (I barely have time to contribute to the one project I maintain)

    original

    • sk@utsukta.org ⁨2⁩ ⁨days⁩ ago

      as long as developers are aware of limitations and shortcomings of LLMs in coding, have an understanding of best practices in coding, and are upfront about how they use coding agents, i don't think there is  an issue with such projects or using such tools responsibly

      original
  • irmadlad@lemmy.world ⁨2⁩ ⁨days⁩ ago

    I think vibe coded projects need at least 6 months to a year of history before they replace anything critical in my stack.

    Reasonable. I do the same with updates. I wait for all the early adopters work out all the bugs, and when I feel comfortable, I update.

    original