Thread

AI coding has made CI a bottleneck, so we reworked ours to keep up

317 points · 408 comments · julian_digital

aliclark · 1790022508 · focus · HN ↗
In my case it's not the CI that's the bottleneck. It's the human testing side. Does it work, sure. But does it actually do the thing we want (and more importantly) does it do it in a way our customers will understand and actually like?
1. shykes · 1790024496 · focus · HN ↗
  Think of it as a layered problem. If the bottom layer (CI) cannot keep up with the output of agents, then solving problems at a higher layer - like user experience checks - will be exponentially slower and less reliable. Kind of like how optimizing tight inner loops makes your whole program faster.
  1. Sharlin · 1790024638 · focus · HN ↗
    Uh, no. If stage X is the bottleneck, it's immaterial how much you speed up stage Y.
    shykes · 1790025015 · focus · HN ↗
    You're assuming QA reviews won't be fully automated, and triggered from a CI pipeline.
    oblio · 1790025120 · focus · HN ↗
    We can assume lots of things, but at some point the rubber must hit the road.
    What exactly are you using to back up this claim?
    > QA reviews [...] fully automated

Unofficial Hacker News client; not affiliated with Y Combinator.