this post was submitted on 27 Jun 2026
423 points (98.2% liked)

Technology

87598 readers
3638 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Epp@lemmus.org 22 points 2 months ago* (last edited 2 months ago) (19 children)

It seems I'm the only software engineer on Lemmy who loves having AI. It's not perfect, but it's so much better than doing everything from scratch and it's far more reliable for solving obscure runtime errors than chasing down all the typically dead-end results on a search engine for the stack trace. Or maybe I'm just the only one willing to endure the down votes. Either way, AI has been an exceptional boon in my daily workload.

[–] JordanZ@lemmy.world 15 points 2 months ago* (last edited 1 month ago) (5 children)
[–] phutatorius@lemmy.zip 7 points 2 months ago (1 children)

When 60-80% or so of your PR can be refactored away then it’s a crap PR and honestly never should have been one.

So their time savings in getting AI help to write their code means that you spend more of your presumably more expensive time doing reviews and educating them about slop removal instead of some higher-value activity. Sounds like you're veering into negative ROI for the AI use if that's true.

Luckily, I don't review PRs very often, I have people to do that. But the general principle is that the content of a PR is the responsibility of the submitter, regardless of its source. Wrong algorithm? Their fault. No-good UTs? Their fault. Inappropriate or unsafe dependencies? Their fault. Slop? Their fault.

Luckily, with the work we do, there's often nothing someone could train an LLM on, so we don't see all that many PRs with AI-generated content, unless we're using some well-known commodity library or framework in a common way. And that was always the easy stuff anyway.

[–] sunnie@slrpnk.net 3 points 2 months ago

A slop PR should be the submitter’s responsibility, but if they’re trying to push out unreviewed slop, you know they’re just going to ask an LLM to refactor it instead of looking at it themselves. The best response is just to reject it outright and have someone else work on a new solution.

load more comments (3 replies)
load more comments (16 replies)