Login
You're viewing the adforward.org public feed.
  • Nov 8, 2026, 6:07 PM

    I don't know how to say this in a good way, while I am pretty excited for the future of this whole thing of vibe coding and it's power, it's extremely sad to see the powerlessness that it accords to the developer. Just some minits ago, I read a post from a developer that has added over 30 feature to their program in 1 week, but only use a fraction of them. The fact that we are very much left out from being a user of our own stuff is really saddening. Maybe this is too far fetch, but we are in a future in which we are a kin to a corporation that produce food for the mass that they themselves wouldnt eat at the first place. We create so much consumption, but we consume very little from it. We are not the intended user nor even a user of our own vibe coded solution, we can't really know not only what is coded, but how our program works, even in a high level. That's, to me, the thing that we less talk about.
    Yes, it's our idea, and yes, maybe it's our guided design, but we are still left out from being a faithful user of our product.
    This is mainly due to the nonstop production that leads to very less consumption.

    💬 1🔄 0⭐ 0

Replies

  • Nov 8, 2026, 6:10 PM

    @kaveinthran For the record, I use most features in blindRadio. I just don't make a point of recording radio. IT's there for those who use it. They can tell me or submit issues or pr's if something doesn't work.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:15 PM

    @kaveinthran It's not out of excusable territory though. Like you can't expect a dev to use every single feature in their app. Unrelated things can revert sometimes when you make a change, maybe you didn't realize until the problem was brought up to you. Even regular coders can miss a feature changing that 0.5% of their users use, and they don't use themselves.

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:18 PM

    @kaveinthran I mean there's a point where what you're saying makes sence. I don't like to put something up on Github until enough of things inside of it works as it should.

    💬 1🔄 0⭐ 0
  • Nov 8, 2026, 6:20 PM

    @serrebi My larger worry is that, the speed of this vibe coding wouldn't give much space for the developer to really explore, test, and deliberate on their work.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 8, 2026, 7:16 PM

    @kaveinthran Practically it's been upon users to test and report issues. Devs mostly develop, with or without bugs. And bugs have always been their, with or without AI. @serrebi

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:19 PM

    @serrebi @kaveinthran I mean, I don't use a lot of features in Freight Fate, like manual shifting etc. I don't like FIreside Patience in Wicket's, but I did play it enough to test to make sure it works and is playable enough for those who do. There are more table games coming which I do like, like Blackjack etc.

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:20 PM

    @Orinks Yeah you obviously test what you can in your apps. I do the same thing because I don't like just putting something up that I feel is incomplete. @kaveinthran

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:50 PM

    @kaveinthran @GoemonIshikawa I mean if you’re adding features and then not using them, maybe ask yourself why, and if that feature should be in your program. This goes for tools written by AI or by hand. Of course, if you’re making those changes because you are being paid to make them, that’s different.

    💬 0🔄 0⭐ 0