this post was submitted on 01 May 2026
75 points (98.7% liked)

Technology

84299 readers
3646 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Corkyskog@sh.itjust.works 1 points 1 day ago (1 children)

I wonder if someone will make bank by playing around with AI coding enough to understand what errors AI is most likely to make and then just market your services and contract out for emergency AI fixes. Tons of stress and would have to manage your own benefits, but I imagine oodles of money.

[–] AA5B@lemmy.world 1 points 1 day ago* (last edited 1 day ago)

My company is working on one such product. So far AI has essentially no guardrails so can too easily go from potentially helpful to harmful. There’s nothing keeping it from sharing confidential data, like customer data, nothing looking at whatever dreck it’s pulling in from the internet, and nothing keeping it from doing harm internally. We can do that.

But most of the more immediate harm is poor practices that we’ve known for decades. Maybe consultants can make bank by pushing best practices we should have followed all along. That article that keeps coming around Lemmy about losing their production database and backup in 9 seconds is a great example. Sure, that LLM needed guardrails to stop that, but any normal best practices would also have prevented that

I’ve seen some baby steps

  • LLMs with “planning” mode that shouldn’t make changes until approved ….. except when they ignore that
  • IDEs with sandbox where you need to whitelist allowed LLM invocations, except there’s too much noise so too many people allow all
  • MCP servers with a read-only mode, or allowing configuring credentials to be read-only