• 8 Posts
  • 126 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle



  • If you can’t drop the use of AI for your own learning, use it for learning. Tell it specifically that you want guidance on how to do something, not to do it for you, perhaps have it create a html guide you can follow without it giving you all the answers.

    If it does something in a way you didn’t expect, ask why. Ask if the way it has done something is the best way of doing it, and then do a bit of research and challenge it when it’s wrong, and it will definitely be at times.



  • Many years ago when I was on a trip to America I visited Brick Lane Curry House to do the Phaal challenge. It was described as excruciatingly hot. I’ve had a Phaal in the UK, and suffered through it.

    They brought the dish out and it was no hotter than a UK vindaloo. I was quite disappointed when they gave me the Phaal curry monster certificate, I’d genuinely hoped for a challenge.



  • Not sure on the size of your team, but you could perhaps form a small subset of AI “champions” who can try to help drive new initiatives. Just some ideas:

    1. Start out with foundational usage of AI agents, ensure people have the right mindset and ownership of using the ai agents. Ensure there is always a “human in the loop.”

    2. Arrange for some training for people (not just Devs) on the right way of using AI, such as not throwing sensitive information into it. Educate people that it’s far from perfect

    3. Get standard boundaries in place for your current and future projects, get context files (agent.md) for your projects so those who do use the agents will be doing so from the best position.

    4. See if you can arrange with the higher ups to arrange some company time do a Hackathon with the use of AI to help people see what they can do with it and the challenges they’ll face. You can also take some learnings from it.

    The way I see it, you’ve been given the position of head of AI because you’re indifferent. It’s your job now to drive engagement (because that’s what your bosses want) but in a controlled manner. If they put someone that was overly enthusiastic about AI they would end up with a huge bill and lots of AI mess to clean up.






  • Machines cannot take responsibility for problems, which is why I feel containment barriers cannot be entirely AI.

    Where I work AI is being pushed hard, but the company has made it their policy that there must be a human in the loop. Ownership of the code written by AI is down to the person using the AI. “Oops, don’t know why the AI wrote that!” Is not a valid answer to bugs being introduced into production.

    I’m seeing senior engineers of 15+ years no longer writing code and churning out a ton more work. They are disappointed they don’t write code anymore but working with the AI is the job they have to do to be able to afford to live. They say the cognitive load has shot up for them, they are constantly spinning plates.

    To make the plate spinning job easier they have implemented guard rails to ensure the agents don’t do anything stupid. I’m seeing a number of stories posted to Lemmy where the AI does dumb shit but the stories don’t apply any accountability to the developers using it.