this post was submitted on 15 Nov 2026
996 points (98.2% liked)

Technology

89835 readers
3840 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
[–] aksdb@lemmy.world 4 points 17 hours ago (1 children)

I think this is a real dilemma: do you contribute to an existing project, going through the motions of creating pull requests and having discussions or do you just make it yourself.

This might be surprisingly where a coding agent could motivate me. I typically don't contribute, because in most of the cases I had the urge to get a missing feature into some piece of software, I had to sink countless hours into understanding their code, getting used to their style, bitching about the choices they made, and/or even setting up a dev environment to test the stuff in (which is often extremely badly (i.e. not at all) documented). This then quickly leads to not-invented-here-syndrome. With a coding agent however, almost all of this becomes irrelevant. The agent can figure out how to run it locally. It can figure out within seconds where in the code I need to make adjustments. If I don't find an explanation for something in the code, I don't have to search for ages, I can let the agent do the semantic search in a fraction of the time. Now I can focus on what I actually wanted to do: develop the feature, not doing code archeology for hours.

[–] jj4211@lemmy.world 1 points 4 hours ago* (last edited 4 hours ago) (1 children)

Just so long as your ultimate pull request is plausibly human viable.

Have been fighting someone because they submitted a 15,000 line pull request for 'one' feature and no one is going to review that mess. I gave a very quick 'for example' showing in the first 30 lines of changes that it's screwing around with stuff that has nothing to do with what the sloperator said they pointed out.

Now they are complaining that I won't take code even though Claude audited it and said it is all good...

(This is work, so I don't have the luxury of just permanently ignoring them).

[–] aksdb@lemmy.world 1 points 3 hours ago

How senior are you? How much senior backing do you have? Close the PR with the comment "unreviewable". Either they provider smaller chunks, or they can fuck off. If they are unable to prompt properly, that's on them. They can use Claude all they want, but they should learn how to.