this post was submitted on 02 Apr 2026
15 points (94.1% liked)

Programming

26326 readers
252 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] TehPers@beehaw.org 7 points 1 day ago

The success rate of main branch builds compounds this further. It has fallen to 70.8%, its lowest in over five years – 30% of attempts to merge code for production are now failing.

...

The integration bottleneck finding is credible. If you’re generating code faster than your team can review and integrate it, that’s a genuine problem this data is consistent with.

I disagree here. If more attempts are failing, then more attempts are needed to merge a branch. If the pipeline is running more and fewer branches are merging, it's also possible that people need to go through more revisions to merge their code than they needed to before.

People using AI to write their entire PR will find that fixing issues with it takes more work. They often don't know how the PR works. I wouldn't be surprised if this resulted in PRs taking longer to merge as a result, which would contradict CircleCI's claims of teams benefiting from AI.

I believe the report has insufficient data to draw any meaningful conclusions. The data is interesting, at least.