• reksas@sopuli.xyz
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    8 hours ago

    to me, vibe coding seems better used to provide a draft of the work so people with actual skills can then do the final work. A draft made with crayons, dogshit and stale beer but draft none the less.

    Or you could just describe what you want to someone who knows how to design code stuff and can ask clarifying questions.

    • Adalast@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      29 minutes ago

      I made this comment on a previous post. Vibe Coding is to Coding as Previsualization (Previs is to Visual Effects. (Previs description) A quick slap job that is used to make sure timing is correct, on set assets will all work, and to communicate to artists, directors, producers, and on-set operators what is expected. It is entirely separate from the final product and nothing ever crosses the barrier between Preproduction and Production.

    • kamstrup@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      2 hours ago

      9 times out of 10, this “vibe draft” sends people down a terrible path that they would have never ventured had there been an adult in the room. I swear I review so much code that sets off in the wrong direction because of this, and I am sick of it.

        • Boo@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          2 hours ago

          But if you get the framing from the terrible prototype/draft, it can lead you into a bad direction. It is like the “Don’t think of an Elephant”. Once you see the “Elephant” you will struggle not to make something that looks more like an Elephant.

          • NιƙƙιDιɱҽʂ@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 hour ago

            True, but I see it more as a tool for a non-technical person to make a prototype of a user experience more than making a foundation for how a project will actually be built and designed from a code perspective. Like, when it comes to the actual implementation of said project, the developer(s) shouldn’t even look at the prototype code. I envision, in this example, as it solely being a tool for non-technical people to express their ideas to the technical side of the operation.

            I agree with you though, that still has potential to pollute a project entirely, and we already have methods of creating requirements and documentation for projects so this isn’t exactly the most useful thing ever.