• Solumbran@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    11 hours ago

    There can be a million papers on how AI is worthless, the vibe coders are way too brainwashed into their shitty habits that they’ll never stop. It’s basically a sect at this point, but a sect that is destroying the world.

    • iocase@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      8 hours ago

      I’ve coded “professionally” (solo dev for a small company. Not the full dev experience so big caveat)

      I find AI is amazing at writing unit tests and other test harnesses. That’s all it’s good for besides summarizing documentation and even then it’s so misleading it’s basically useless you have to constantly doubt it. It’s a pathological liar… And I mean it’s kind of an impossible task… It’s trained on the entire internet. The strongest weights it has are for the oldest and most popular libraries. Oftentimes it’s telling me to use deprecated shit left and right because that’s biased extremely high during training, and maybe 1% of posts on that library mention it’s deprecation.

      I prefer to write my code the old fashioned way. If I have it generate code it’s never pasted in, and I prefer having it explain what I don’t know about what it’s doing. Using it as an assistant and a TDD buddy works relatively well.

      Also if you poke at software architecture. I’ve learned a lot (I wasn’t formally schooled in computer science) and it’s good as long as you constrain the scope of what you’re asking about, and make sure to consider it on your own against the existing project architecture. I still make the design decisions myself.

      Oh, also having it make design decision documents. I often make those to record “this is why I’m doing this feature this way. These are the options I considered, and why I decided my way is better in this particular case” so I have a record of my state of mind and decision making.

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 hours ago

      There are papers that are pro and con. It’s a new tech - we’re still figuring out how to use it. It’s gotten a lot better than a year or two ago though.

      It’s definitely helped me get things done a lot faster. You can point to “that one study everyone does” and tell me “no it’s not” but honestly, it is.

      I’ll give you an example - I had to write a small bash script to fix home directory ownership on a server because somebody borked it and some critical jobs weren’t launching properly. Just something to read /etc/passwd, parse out the owner and home dir and chown-R $user $home. Dozens of user dirs so quicker to just script it.

      Time was of the essence. Claude had a script in ~6 seconds. Yeah - I could have written it - but not that fast. I validated the output and gave it a run. All’s good.

      You can insult me as “not good developer” or whatever you need to do to make yourself feel better - your opinion of me is irrelevant. But these tools are pretty damn good at what they do if you use them properly. “Properly” being the key word here. They are tools not employees so you need the proper critical thinking to apply them effectively.

      • Solumbran@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 hour ago

        It’s funny how everyone that tries to defend the use of AI, other than deny the fact that most evidence (and common sense/basic understanding of AIs) points to the idea that it’s just negative, always avoid the subject of environment.

        Even if you assumed that you get the same result with Claude or whatever in 6 seconds, and with your brain in five minutes… Is the end of humanity and a massive extinction event worth those 5 minutes?

        Defending AI while there are literally news popping out right now about heat waves being more violent than ever recorded and killing thousands of people per day in countries that had no problems with heat a few decades ago, is extremely selfish and self-centered. And the only justification is “it’s a bit faster and easier”. Okay.

      • iocase@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        8 hours ago

        Yeah this is the type of constrained use case I use it for too. Same with unit tests and testing in general.

  • Lovable Sidekick@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    13 hours ago

    I’m a retired software dev, but anactive developer I know talks about how much time he saves daily by using Claude for grunt work.

    • sobchak@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      6 hours ago

      I’ve tried (and still try) to find good workflows using AI, but I don’t think I’ve found anything that saves time. To get the same quality using AI, I have to go back and forth with it a lot, and review all the bloated bullshit it generates. If you don’t care about quality or the thing even working correctly (e.g. prototypes/POCs), it’s really fast.

        • Dumhuvud@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          26 minutes ago

          You aren’t prompting right, bruh. You need to be very good at writing markdown to leverage Ayy-Eye properly.

          You aren’t using the latest and the greatest model, bruh. Have you tried Claude Fairy Tale 6.9.420?

    • toofpic@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      12 hours ago

      Most of the younger generation devs at my company are using ai coding - mostly for said gruntwork (like writing small functions, api methods, writing what data they want to see instead of complex sql requests), but some are more enthusiastic and use heavier agentic setups. The best validation is that we still have old-school human pull request reviews (enforced by a scary Chief R&D) and if your colleague would see something unreadable or weird, your stuff wouldn’t pass.
      I’m a Product Manager and I have several pet products now - all pretty viable (depending on the time I invested in each of course). A stocks website, a money splitting android app (now passing google play review), a weather app. All working, and I have really low coding skills myself

      • iocase@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        8 hours ago

        AI corporate slop is when you mass generate a bunch of stuff, don’t read it, and then export the mental burden to a different coworker. You make them looks less productive and you look extremely productive, when really you’re stealing the productivity of colleagues.

        You just reminded me of that.

        • toofpic@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          14 minutes ago

          Again, in a corporate setting I see that the “generated stuff” is being read before being approved. And in my private setting I’m working on my projects for myself, I’m not “stealing the productivity”, I obtained productivity. All my life I was coming up with ideas, planning, and managing, but having something on my own wasn’t possible - I can’t hire a dev team. Now I am my team, I’m empowered.

    • hperrin@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      12 hours ago

      Tell him this: If you’re writing that much boilerplate (grunt work), you’re probably doing something wrong. If AI can write your normal work, you really should be learning, so not using AI at all.

      • Lovable Sidekick@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        12 hours ago

        Actually I’m not going to tell a dev with decades of experience that an internet rando thinks he’s doing his job wrong lol.

        • hperrin@lemmy.ca
          link
          fedilink
          English
          arrow-up
          0
          ·
          12 hours ago

          K. It’s astounding to me that after decades in the business, he’s still writing code that can be written by basically an intern.

          When I try to get AI to write my code, it stumbles all over itself just failing to understand the simplest of my libraries. (Literally it made multiple mistakes using the fucking tokenizer library I wrote that is so simple, an intern would have no problem with it.)

          • Lovable Sidekick@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            11 hours ago

            he’s still writing code that can be written by basically an intern He usually does full-stack projects by himself, so he has to do everything. And he’s using AI to do what interns could do. I’ve dabbled a little using VSCode AI myself to refactor and upgrade a couple hobby projects, and it didn’t “stumble all over itself” at all. In fact it conversed with me like an intern or colleague would, and made many proposals I agreed with. There are ways to craft your prompts that make AI work better. Maybe that’s your problem I dunno.

            • hperrin@lemmy.ca
              link
              fedilink
              English
              arrow-up
              0
              ·
              7 hours ago

              Even if it does write code that works, it usually (about 50% of the time in my experience) has bugs, and sometimes those bugs can be really difficult to spot. For me, it has never saved me any time. I’m either fixing something it doesn’t know how to do correctly, or going over its code with a fine tooth comb because when it says, “this is production ready code, with no bugs,” it’s usually wrong. That takes a lot of time. It’s easier for me to just write the code correctly myself.

              Admittedly, I haven’t used that new model that Anthropic revoked access to the public to recently. Maybe that one is good enough for government work.

              • Lovable Sidekick@lemmy.world
                link
                fedilink
                English
                arrow-up
                0
                ·
                4 hours ago

                When I first tried it I felt lost, but after watching a couple videos about writing good prompts I had no trouble getting it to produce perfectly good code that did what I wanted. Your mileage may vary.