Comment on I Went All-In on AI. The MIT Study Is Right.

• embed_me@programming.dev ⁨2⁩ ⁨weeks⁩ ago

  Vibe coders can’t debug code because they can’t write code

  source

  • _g_be@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Yes, this is what I intended to write but I submitted it hastily.

    Its like a catch-22, they can’t write code so they vibecode, but to maintain vibed code you would necessarily need to write code to understand what’s actually happening

    source
• Evotech@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  I don’t get this argument. Isn’t the whole point that the ai will debug and implement small changes too?

  source

  • yuki2501@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Think an interior designer having to reengineer the columns and load bearing walls of a masonry construction.

    What are the proportions of cement and gravel for the mortar? What type of bricks to use? Do they comply with the PSI requirements? What caliber should the rebars be? What considerations for the pouring of concrete? Where to put the columns? What thickness? Will the building fall?

    “I don’t know that shit, I only design the color and texture of the walls!”

    And that, my friends, is why vibe coding fails.

    And it’s even worse: Because there are things you can more or less guess and research. The really bad part is the things you should know about but don’t even know they are a thing!

    Unknown unknowns: Thread synchronization, ACID transactions, resiliency patterns. That’s the REALLY SCARY part. Write code? Okay, sure, let’s give the AI a chance. Write stable, resilient code with fault tolerance, and EASY TO MAINTAIN? Nope. You’re fucked. Now the engineers are gone and the newbies are in charge of fixing bad code built by an alien intelligence that didn’t do its own homework and it’s easier to rewrite everything from scratch.

    source

    • Evotech@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

      If you need to refractor your program you might aswell start from the beginning

      source