• boolean_sledgehammer@lemmy.world
    0·
    5 months ago

    Prompt an LLM to write a bit of code that does something. Do this 9000 times until it spits out something that vaguely accomplishes this task. You can’t push any of the fever dream nonsense it created into the main branch until you check it thoroughly. In the end you spend more time with this process than you would have if you’d just written it yourself.

    The C suite and the board members continue jerking each other off as they call this “efficiency.”

    • Konstant@lemmy.world
      0·
      5 months ago

      “Vibe coding” is an informal term, mostly used in online programming communities, that refers to writing code in a relaxed, intuitive, or improvisational way rather than following a strict plan or methodology.

      It’s often associated with:

      Experimentation → typing out ideas, running them quickly, and adjusting on the fly.

      Flow state → coding while listening to music, late at night, or just for fun without rigid structure.

      Prioritizing creativity over rules → not worrying too much about best practices, efficiency, or readability at first—just “feeling out” the solution.

      Playfulness → sometimes it means coding with minimal context, like making something cool without knowing exactly how it’ll end up.

      Some people use “vibe coding” positively (as in getting into the zone and letting intuition guide you), while others use it humorously or critically (as in writing spaghetti code without much forethought).

      Would you like me to give you some examples of how vibe coding looks in practice—like snippets that show the contrast between “structured coding” vs. “vibe coding”?

  • FartMaster69@lemmy.dbzer0.comEnglish
    0·
    5 months ago

    It’s using AI to ruin your codebase and built technical debt.

    I think it is very funny and fully support companies doing this to themselves.

      • wischi@programming.dev
        0·
        5 months ago

        I think the most hilarious thing was their public Copilot demonstration working on the .NET source code. They basically showed the world that copilot isn’t ready for serious work.

      • marcos@lemmy.world
        0·
        5 months ago

        It were they that have been bragging that more than 50% of their code was written by AI, weren’t?

        Anyway, that’s counted by lines of code, not in number of mini-vans. They can still use a better statistic.

  • Rose@slrpnk.net
    0·
    5 months ago

    Original definition: using AI to create a small bespoke kinda-crap-but-it-works apps or games for personal use. It’s a shitty proto but it’s interesting.

    (My reaction: ooo not my jam but that sounds neat I guess)

    Modern definition: it’s a multi-quadrispillion dollar industry and it’s the future according to some very important board members.

    (My reaction: …capitalism ruins fucking everything)

  • JumpyWombat@lemmy.ml
    0·
    5 months ago

    If you need a quick&dirty piece of code, you can generate it by firing some prompts into an LLM. You can get a decent result if you know what you are doing. It may not be production-ready, but often it’s a good starting point. This is NOT vibe coding.

    Vibe coding is what people who don’t know what they are doing do when they try the process above, and think it’s production-ready.

  • m532@lemmygrad.ml
    0·
    5 months ago

    Its a strawman made up by copyright crusaders, to belittle people who use new technology.

  • Hexarei@beehaw.org
    0·
    5 months ago

    It’s using tools like Claude or other agentic AI to collaboratively make an app. It’s a fun novelty until you realize people paid more than you are doing it without knowing what they’re doing and getting away with it.

  • janAkali@lemmy.sdf.org
    0·
    5 months ago

    Vibecoding:

    • go to chatgpt
    • ask it to make an app
    • ask it to fix errors (ad infinitum)
    • ???
    • sell app (optional)
    • get sued and ruin your reputation (hopefully)
    • TORFdot0@lemmy.worldEnglish
      0·
      5 months ago

      The ??? isn’t a reference to underpants gnomes. It’s just that no one has ever gotten LLMs to actually fix its own bugs to find out what that step is

  • sacredfire@programming.dev
    0·
    5 months ago

    I remember when the term was first coined and it meant something like “asking an llm to code and NOT attempting to validate, fix or correct the outputs yourself. Just keep prompting in natural language until it works.” It was supposed to be a joke - this sort of use hits a wall pretty quickly and illustrates how limited llms can be.

    The term has taken off and its meaning is now in flux. I did find it particularly amusing seeing all the LinkedIn lunatics start posting LLM written garbage about “integrating vibe coding Into your workflow” because they thought it was the new buzz word… and I guess they were right.

  • the_q@lemmy.zip
    0·
    5 months ago

    It’s going to an llm and typing in the text box “make me an app that does X” then patting yourself on the back for “coding”.