• SpaceCowboy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 hours ago

    I find writing the code is the easy part. The difficult part is figuring out what the requirements are, fitting together all of the data relationships, figuring out the security so the correct people and systems have access to the data. To do these things I need very specific knowledge of the systems I’m working on, knowledge the AI doesn’t have.

    I could see it could give you a simple interface that’s similar to something it’s been trained on. But it’s capabilities are very limited in terms of doing anything novel. It can’t actually understand a problem, it can only give some code similar to problems that exist in it’s training data. Sometimes that’s useful, since at times I do have to solve problems that’s been solved by others. But most of the time the AI can’t understand what I’m trying to do and it’s easier to write the code than it is to try to explain to an LLM how to write the code I want it to write.

    • kamee@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      Maybe you are doing some exotic stuff, but for me it’s more than capable of writing code, coding is mostly about applying existing patterns to solve known problems, very few programmers deal with novel problems.

      Design Patterns book has been out for what? 2 decades, and it’s not outdated.

      For good team interoperability you want to have code that’s standardized, that’s also where LLMs excel at.

      It’s a nice productivity tool, just like an IDE is a nice productivity tool