‹ BackHN Continuity

Thread

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

317 points · 408 comments · julian_digital

  1. xracy · · focus · HN ↗
    Maybe I'm alone in this, but as someone who is in tech, I don't know what CI is, and I don't think it's unreasonable to expect it to have an expansion within the article the first time you use it...

    AI is in the cultural zeitgeist, but you gotta expand most other things at least once.

    1. handfuloflight · · focus · HN ↗
      So if you don't know what CI is, what does "I am someone in tech", mean? Marques Brownlee probably doesn't know CI is, but he's also in tech. Because if you by mean "I am in tech" that "I am a software engineer", and you don't know what CI is, then boy; I'd be worried for you.
      1. Retric · · focus · HN ↗
        CI is really only significant on the programming side of things. Networking, systems administration, hardware, etc often don’t have that workflow.
        1. Asmod4n · · focus · HN ↗
          sysadmins CI is hoping the machine still boots after an update. Unless you are lucky you got two identical machines to have a test env.
          1. to11mtm · · focus · HN ↗
            Also the case of 'learning that someone did updates directly on AWS console instead of terraform and losing 0.5 or more days cleaning up the resulting mess'
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.