- YouTube
www.youtube.com
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
  • Lovable Sidekick@lemmy.worldEnglish
    2·
    2 days 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.caEnglish
      4·
      1 day 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.

      • toofpic@lemmy.world
        2·
        1 day ago

        Fable was “just ask and get it done” quality level, but really I don’t get THAT much bugs - about the same amount that I see irl developers do: get a new feature, find 5 problems, get them fixed, find one more, done. As a recommendation - try to alleviate the biggest problems that ai models have:

        • overconfidence - skipping wrong stuff “because they have a note saved that it works” or losing the point where they stopped after a session broke, then making things up. Test Driven Development solves the majority of problems like that - when Claude writes tests first, then it’s not able to bullshit me that the job is done when “everything is red”
        • even with large contexts, they run out and stuff gets lost. So if you’re not doing something really compact, make your ai document everything, document the feature they are working on now, make it then offload it to permanent doc when that piece is finished. When the ai will fuck up next time, you can tell it to “go read some docs” and most of the times it will work
        • hperrin@lemmy.caEnglish
          3·
          21 hours ago

          I’m glad it works for you, but it simply does not work for me. Maybe you could try yourself on some of my libraries, because I have never gotten it to save me any time. It’s just spending money and making the work less fun for no reason. Oh, also not having the copyrights to the things that go in my code base, don’t forget that.

      • Lovable Sidekick@lemmy.worldEnglish
        2·
        1 day 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.

        • x74sys@programming.dev
          3·
          1 day ago

          Honestly, I think what you consider „good code“ is just shifted from what the previous commenter considers „good code“. Prompting is about giving enough information so the AI can solve the task without needing to reconstruct a lot of context. Most people using AI somewhat regularly will have figured out to write good enough prompts. I‘ve never seen AI generate perfectly good code beyond hello world and the fibonacci sequence. And by perfectly good I mean I wouldn’t change beyond 30% of what it produces, which is not a high bar.

          • Lovable Sidekick@lemmy.worldEnglish
            1·
            16 hours ago

            The last thing I had it do was create a filesystem using Discord as the storage medium. Don’t ask me to justify the approach or tell me it breaks Discord’s rules - that’s irrelevant to my point. It was a fun idea to explore a way to host a bot for public use without also hosting other people’s data. The data is pretty minimal but does involve several small tables with relational links. I thought it would be interesting to store it as a few Discord messages in a private channel.

            As sample data I gave the AI the JSON file I had been using locally, and discussed various aspects of the design with it. It came up with the scheme of splitting up the data using a channel for each table and a message for each row. I don’t remember the interaction in detail but it asked me a bunch of questions - for example, it commented that Discord’s limit of 2000 characters per message didn’t seem to be a problem given the sample data, but wanting me to confirm. I had it generate the code as a node module with complete CRUD functionality, and refactor my existing code to use the module instead of the JSON file. What it gave me worked perfectly right away.

            Now of course this isn’t “Write me an accounting system,” but it’s far more complex than Hello World or Fibonnacci. Whether or not you code with AI is your choice, but deciding my notion of quality isn’t up to someone else’s because my results aren’t “AI sucks” is just pure denialism.