this post was submitted on 22 Aug 2026
472 points (97.2% liked)
Technology
87450 readers
3619 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My coworkers use Claude like an actual brain subscription, and I have started to write off everything they say as if it came straight from the AI. They have gained so much unearned confidence about shit they have no idea about, and have even argued with the development team about it.
I got into an argument about how in band and out of band DTMF work with one of them for a solid half hour before they finally admitted they didn't actually know but were going off what claude said.
I wanted to punch them for wasting everyone's time. If you don't understand stop answering definitively like you're the expert.
Some customers have switched to using AI emails too. Customers that used to ask extremely low level questions will now submit a 2 page long email with action items and explinations about why our product does X, Y, Z, and I have to read it twice to figure out their problem isn't even in the action items because the AI hyper focused on the wrong thing.
Like ok thanks you dumped the entire app log into Claude and asked it "why no work" and Claude read an error message that's benign and now the customer is demanding fixes for something that is not and never has been a problem and won't actually solve the root issue.
When we started cooperating with a team in India, we had to clean up our logs to reclassify those "errors that are not a problem" because we end up endlessly re-explaining to every new engineer they hire how "ERROR doesn't indicate a problem in this situation." No, writing docs explaining that and assigning said docs as required training ALSO did not help.
But just think of those billable hours