‹ 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. madrox · · focus · HN ↗
      I recommend making a habit of googling or asking AI about terms you run into. As someone who is in tech, you will hear tech jargon your whole career that will not be explained if it's considered standard terminology for the audience being spoken to. It is better to learn to educate yourself than expect others to go out of their way.
      1. xracy · · focus · HN ↗
        It's wild to me that people think asking for

        "Continuous Integration (CI)"

        in the first line of a paragraph of a long article is "going out of your way". It used to be the standard expectation for using shorthand.

        1. ben0x539 · · focus · HN ↗
          I don't think it would occur to me to write out Continuous Integration because it's basically a nonsense term if you don't know what it means anyway, it's not any less opaque than just CI. The problem isn't the shorthand here, but yeah it's probably good to spell it out anyway so when someone googles it they have more confidence they've found the right thing.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.