Minimum Vibable Product… I’ll see myself out now

  • lime!@feddit.nu
    link
    fedilink
    English
    arrow-up
    9
    ·
    4 days ago

    oh hey an actual joke in programmer_humor, let’s check the comments

  • The Bard in Green@lemmy.starlightkel.xyz
    link
    fedilink
    arrow-up
    34
    ·
    edit-2
    6 days ago

    My experience working with a vibe coder hired by one of our clients is actually that’s it great for MAXIMUM VP, as in a viable product made up of just under 40k lines of typescript, plus 90+ Node libraries for an app that amounts to a login page, a Square payment gateway and a user settings page (it’s seriously just a signup page for a coastguard and weather alerts service that the rest of our team built in Python and Rust). It crashes if it can’t talk to a database server that hosts no actual databases. It crashes if it doesn’t have the Square API secrets as envars, but the LLM also hard coded them into the API calls. It actually crashes if you try to run it any way other than “npm run dev” (so I srsly set up a service that runs it as npm run dev, as the ubuntu user).

  • Pup Biru@aussie.zone
    link
    fedilink
    English
    arrow-up
    24
    ·
    5 days ago

    vibe coding is trash for MVPs… it’ll get you there, but as always the achilles heel of vibe coding is maintenance and bugs

    vibe coding is great for a POC, but the defining difference between a POC and an MVP is that a POC is made to be thrown out, doesn’t have to work all the time (you can say “ah yup just need to give it a kick” when you’re showing it off and manually intervene)

    vibe coding is good to show a basic, unmaintainable, non-production version of a feature of function, but then you need to take that and manually build it into your MVP - perhaps by copying some minor parts of the POC, but verifying every step

      • Pup Biru@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 days ago

        yeah viable is such a variable concept

        i guess like… i have a friend that is a lab tech, and he vibe coded a stand alone HTML and JS page for their team to take CSV and filter it… the excel process they used before was horrendous… in that case, i guess that’s a viable product: it works, isn’t buggy (or at least bugs will become well known and able to be manually avoided or worked around)… i’d say that’s an MVP but wouldn’t be so if you wanted to productise it

    • als@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      4
      ·
      5 days ago

      Damn, you really shouldn’t say that people of colour are made to be thrown out. That’s fucked up (/s)

    • ByteOnBikes@discuss.online
      link
      fedilink
      arrow-up
      3
      ·
      5 days ago

      I took it for a test run to build out a API as a proof of concept to my superiors to show what we can do.

      I then started on a real version, saving the vibe code version as a backup in case I could cherrypick code.

      After recreating the basic functionality again but properly, I looked at the vibe coded project and threw it in the trash. Had zero reusability.

    • null@lemmy.nullspace.lol
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 days ago

      Even before that, it’s great for bouncing abstract ideas around for how you might go about defining that POC.

  • sbird@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    5 days ago

    I don’t want to be that guy, but ‘s is for possession, or when it is short for “is”, like what’s or how’s being what is and how is. Just a plain s for plural, never ‘s. I don’t get how so many people get this wrong, it’s not that hard.

    • NeatNit@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      ·
      4 days ago

      I think you are wrong in this case. For example, many people would write X’s when talking about multiple instances of the letter X. As another commenter said, there are exceptions and acronyms can be one of them.

      But I upvoted you anyway because us pedants need to stick together.

        • NeatNit@discuss.tchncs.de
          link
          fedilink
          arrow-up
          2
          ·
          4 days ago

          The cool and/or awful thing about language (not just English) is that if enough people many the same mistake, it’s no longer a mistake!

  • razen@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    4 days ago

    One can do all the vibe coding they need but if they understand nothing what the AI is giving and also not verifying, things can go wrong very quickly.

  • GreenKnight23@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    5 days ago

    know what’s great for MVPs? language specific frameworks like ruby on rails.

    runs like dog shit, but you can have a full fledged app in days or weeks instead of months.

    AI can’t do that.

      • GreenKnight23@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        5 days ago

        agreed.

        modern ruby can even outperform python, php, and others.

        rails is still dog shit slow. but it is better now. considering what rails does though, the performance tradeoff is negligible. proper indexing and query improvements are extremely beneficial to UX.

  • whatwhatwhatwhat@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    6 days ago

    It took me a minute to realize that “MVP” means “most valuable player” to most people.

    Apparently I’ve been in tech far too long, and care about sports far too little.

  • otacon239@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    6 days ago

    I was looking at open-source app builder toolkits the other day and they’re all “ask an AI to build garbage” wrappers. There were way fewer options for toolkit-style visual app builders because those can’t be loosely slapped together in a couple weekends.