this post was submitted on 15 Aug 2026
20 points (100.0% liked)

Programming

28155 readers
22 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
20
Write for people (vickiboykis.com)
submitted 4 days ago by codeinabox@programming.dev to c/programming@programming.dev
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] codeinabox@programming.dev 9 points 4 days ago (2 children)

This sums up my current bugbear with colleagues using Claude, as its output is too verbose. If they are going to use agentic tools, I'd rather that they provided a concise human summary.

But where it starts to get dicey is when you have both jargon and long text explanations being generated by machines, for people at different levels of understanding. “Bumped dependencies” is good. Everyone knows we are updating packages. “Performed a scheduled dependency refresh as part of ongoing maintenance practices. Minor and patch-level version bumps were applied across the dependency graph, including transitive dependencies where applicable” is bad.

[–] Shadow@lemmy.ca 3 points 4 days ago

I've found success in telling Claude to keep it brief and to use https://en.wikipedia.org/wiki/Simplified_Technical_English

[–] a1studmuffin@aussie.zone 2 points 4 days ago

I honestly think this is one of the biggest challenges that needs to be solved. The constant jargon, poor naming choices and assumed prior knowledge of pages of text is extremely fatiguing. It only gets worse as the volume of LLM-generated content in your project increases.