• @jmcs@discuss.tchncs.de
    link
    fedilink
    6
    edit-2
    3 months ago

    Just wait until the vibe coder overwrites 3 months of “work” with garbage because ChatGPT never told them about git and then decided to poop the pants.

  • @MajorHavoc@programming.dev
    link
    fedilink
    5
    edit-2
    3 months ago

    Today I learned the term Vibe Coding. I love it.

    Edit: This article is a treasure.

    The concept of vibe coding elaborates on Karpathy’s claim from 2023 that “the hottest new programming language is English”,

    Claim from 2023?! Lol. I’ve heard (BASIC) that (COBOL) before (Ruby).

    A key part of the definition of vibe coding is that the user accepts code without full understanding.[1] AI researcher Simon Willison said: “If an LLM wrote every line of your code, but you’ve reviewed, tested, and understood it all, that’s not vibe coding in my book—that’s using an LLM as a typing assistant.”[1]

    Did we make it from AI hype to AI dunk in the space of a single Wikipedia article? Lol.

    • Ephera
      link
      fedilink
      English
      53 months ago

      Interesting that the term was coined by someone who presumably intended it to mean a good thing. I assumed it to be an entirely derogatory term…

      • @Ropianos@feddit.org
        link
        fedilink
        4
        edit-2
        3 months ago

        Well, lots of words are sort of derogatory in programming right? Hackers hacking things together, rubber duck debugging (you have a bug? Go talk to a toy!), git blame and probably more

        Edit: forget git blame, git itself is already slang for idiot. As Linus Torvalds once said, he created two successful projects, both named after himself

        • Ephera
          link
          fedilink
          English
          23 months ago

          Sure, but those words have been coined by the nerds, or those that don’t try to sell you anything at least. The guy very much wants to sell you vibe coding and LLMs and whatnot.

    • Mirror Giraffe
      link
      fedilink
      English
      23 months ago

      I’ve ended up becoming the sole caretaker of two react native apps, something I did not ask for but some people were fried.

      I’m not going to manually troubleshoot and learn everything that breaks when I need to update a dependency. I’ll vibe through those errors, learn what I have time for and then test it like mad.

      A lot of the time I end up having to solve things myself but my job wouldn’t be tolerable if I had to manually work that shit.

      • @MajorHavoc@programming.dev
        link
        fedilink
        3
        edit-2
        3 months ago

        Yeah. The “this got dumped on us and we’re doing the minimum until we can replace it” is a genuinely solid use case for vibe coding.

        And honestly, that’s all I usually did with those before AI came along anyway. So I welcome better tools for it.

    • @TechieDamien@lemmy.ml
      link
      fedilink
      13 months ago

      To be fair, sometimes it is right to take the code from the questions. Eg if you want behaviour x and the question is “how do I do y, my code is only doing x?” Then the code you want is from the question.

  • Colonel Panic
    link
    fedilink
    23 months ago

    vibe coding is the dumbest term they could have come up with. can we call it imbecile coding instead?

  • Ephera
    link
    fedilink
    English
    13 months ago

    I mean, surely you did it for the exercise, right? If you needed a solution, you could’ve very likely used a library…

      • Ephera
        link
        fedilink
        English
        13 months ago

        Well, we have a tool for that called vendoring, a.k.a. copy-pasting the library code into your repo. It’s no worse than copy-pasting LLM-generated code…

        • @chicken@lemmy.dbzer0.com
          cake
          link
          fedilink
          1
          edit-2
          3 months ago

          To me the disadvantage would be, the library likely does many more things than just what you need it for, so there is way more code, so you probably can’t realistically read and understand it yourself before incorporating it. This would lead to among other issues the main thing that irritates me about libraries; if it turns out something in it is broken, you are stuck with a much bigger debugging problem where you first have to figure out how someone else’s code is structured.

          Although I guess that doesn’t apply as much to implementations of common algorithms like OP since the library is probably solid. I would consider favoring LLM code over most anything off npm though.

    • @theneverfox@pawb.social
      link
      fedilink
      English
      13 months ago

      I love the in between, where you have to actually adapt algorithms to useful situations

      It’s like 2% of all the work I do, but those moments stick with me