• Two9A@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    So there are multiple people in this thread who state their job is to unfuck what the LLMs are doing. I have a family member who graduated in CS a year ago and is having a hell of a time finding work, how would he go about getting one of these “clean up after the model” jobs?

  • orca@orcas.enjoying.yachts
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I don’t really care about vibe coders but as a dev with just under 2 decades in the field:

    1. Your vibe coding shit will not go to prod until humans fully review it
    2. You better review it yourself first before offloading that massive mental drain to someone else (which means you still need to have some semblance of programming skills). Don’t open a PR with 250 files in it and then tell someone else to validate it.
    3. Use more context. Don’t give it vague ass prompts.
    4. Don’t use auto-accept. That’s just lazy asshole shit.

    I can’t stress this enough: if you give me a PR with tons of new files and expect me to review it when you didn’t even review it yourself, I will 100% reject it and make you do it. If it’s all dumped into a single commit, I will whip your computer into the nearest body of water and tell you to go fish it out.

    I don’t care what AI tool wrote your code. You’re still responsible for it and I will blame you.

    • Adalast@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      I have never used an AI to code and don’t care about being able to do it to the point that I have disabled the buttons that Microsoft crammed into VS Code.

      That said, I do think a better use of AI might be to prepare PRs in logical and reasonable sizes for submission that have coherent contextualization and scope. That way when some dingbat vibe codes their way into a circle jerk that simultaneously crashes from dual memory access and doxxes the entire user base, finding issues is easier to spread out and easier to educate them on why vibe coding is boneheaded.

      I developed for the VFX industry and I see the whole vibe coding thing as akin to storyboards or previs. Those are fast and (often) sloppy representations of the final production which can be used to quickly communicate a concept without massive investment. I see the similarities in this, a vibe code job is sloppy, sometimes incomprehensible, but the finished product could give someone who knew what the fuck they are doing a springboard to write it correctly. So do what the film industry does: keep your previs guys in the basement, feed them occasionally, and tell them to go home when the real work starts. (No shade to previs/SB artists, it is a real craft and vital for the film industry as a whole. I am being flippant about you for commedic effect. Love you guys.)