1261
Companies That Tried to Save Money With AI Are Now Spending a Fortune Hiring People to Fix Its Mistakes (futurism.com)
submitted 1 year ago by to c/technology@lemmy.world
120 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 99 points 1 year ago (7 children)

Vibe coding is 5% asking for code and 95% cleaning up the code, turns out replacing people with AI is exactly the same.

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 17 points 1 year ago (2 children)

    Jup. But the same goes for developers that go way too fast when setting up a project or library. 2-3 months in and everything is a mess. Weird function names, all one letter vars, no inversion of control, hardcoded things etc. Good luck fixing it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 9 points 1 year ago (1 child)

    This is what I fight against every goddamn day, and I get yelled at for fighting against it, but I’m not going to stop. I want to build shit that I can largely forget about (because, you know, it’s reliable and logically extensible and maintainable) after it gets to a mature state, and I’m not shy about making that known. This has led to more than a few significant conflicts over the course of my career. It has also led to me saying “I fucking told you so” more than a few times.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 9 points 1 year ago

    It has also led to me saying “I fucking told you so” more than a few times.

    I have had several situations where I didn't even have to give knowing looks, everybody in the room knew I told them so six months ago and here it is. When that led to problems working with my leadership in the future (which happened more often than not), that was a 100% reliable sign that I would be happier and more successful elsewhere.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 1 year ago

    Stack Exchange coding is 5% finding solutions to try and 95% copy-pasting those solutions into your project, discovering why they don't work for you, and trying the next solution on the search list.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago (2 children)

    I'm still not sure how this is any different than when I used stack exchange for exactly the same thing.

    Well, SE code usually compiled and did what it said. I guess that part is different.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago (1 child)

    Practically negligible then...

    However how the heck have you all been using stack exchange? My questions are typically something along the lines of:

    "How to use a numpy mask with pandas dataframes"

    Not something that gives me 50 lines of code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •