• bigredgiraffe@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    I am in the same boat, long time infrastructure automation engineer as well. Sometimes it’s faster to explain how terraform or whatever needs to act and then fix the issues rather than having to sift through the docs for every provider.

    I also do a similar thing to you with code, I also have to read a lot of other people’s code in languages I don’t know to help troubleshoot things and while I can usually follow the logic it is such a time saver to have AI to read the docs for the libraries and languages for me to at least find the part of the docs I need to read faster than searching myself.

    Overall, I also agree with the sentiment on AI most of the time and all of its criticisms are definitely valid but I think too many people try to use AI to do their work for them instead of using it more like a rubber duck you can program with normal language.

    • Modern_medicine_isnt@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 hours ago

      My new (to me) “revelation” is that AI needs a ton of structure. It’s like a child who when presented with too many options stops thinking and just randomly chooses one to do so they can be done with whatever it is. From what I can tell, the people who make the most use of AI have it tightly controlled. Rules, hooks, and various other tricks to essentially herd AI into doing what it should do. Kinda like herding cats.
      Right now the tools and such for setting up that structure are immature, and best practices are hard to define when the base AI is still changing a lot. For people who are just trying to use AI casually, they have heard the hype, and they think they should expect it to work like a person. When it doesn’t, they just say it sucks. And as a person, it does suck. It’s a tool. And a complex one at that. Seems it requires significant investment to get the most out of it.