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. lbrito · 1790026164 · focus · HN ↗
  I feel no one talks about this, and yet it is glaringly obvious. Are we even solving the right problem? No one cares. Push code. Number go up.
  1. Aeolun · 1790054684 · focus · HN ↗
    That problem isn’t new though. It’s not the biz people that are enthusiastic over AI, it’s the devs.
    mk89 · 1790055074 · focus · HN ↗
    You're so lucky to work for a company where PMs don't vibecode and tell how easy it is to do things....!
    brunoarueira · 1790093469 · focus · HN ↗
    The problem sometimes is even PMs don't know what to do, so vibecode things is just burning tokens without a real goal!
    lbrito · 1790091422 · focus · HN ↗
    Some devs are, some aren't. I've seen some numbers and its more or less a 50/50 split. HN comments kind of confirm that anecdotally.
    Engineers seem to fall within a spectrum between "building" (enjoy the task of designing and programming something) and "completing" (enjoy seeing a finished product). AI enthusiasm correlates neatly with that dimension.

Unofficial Hacker News client; not affiliated with Y Combinator.