conv.

All stories
TechFading · day 3

Linear optimizes CI pipeline as AI agents accelerate code shipping

The development tool company reworked its continuous integration infrastructure to handle code validation at the pace AI coding assistants now generate changes.

What to know

  • AI coding assistants have become so fast at generating code that continuous integration—the automated testing and validation stage—is now the constraint slowing down the development cycle, forcing infrastructure investment.
  • Linear cut pull request validation time to just over 5 minutes through three approaches: moving to faster third-party CI runners (34% speed gain), adopting a native TypeScript compiler (73% faster type-checking), and refactoring lint rules to avoid expensive type-graph building.
  • The optimization reflects a broader tension in AI-accelerated development: tools ship code faster, but the validation, testing, and human product decisions haven't accelerated equally, raising questions about whether speed gains translate to better products.

The dispute Whether AI's measured productivity gains at the infrastructure level (faster CI, more code shipped) translate to meaningful improvements in end products, revenue, or user experience. · positions read across 46 posts and comments

many voices

AI is driving tactical improvements in infrastructure and process automation, though not yet in final product outcomes.

  • “A good chunk of what my company has been doing with AI falls into either burning down our known tech-debt and "easy wins" that no one ever had the bandwidth to approach... And improving / automating our processes.”

    TrueDuality · Hacker News ↗
many voices

Speed gains don't matter if validation and product decisions remain slow; CI optimization alone doesn't solve the real bottleneck.

  • “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?”

    aliclark · Hacker News ↗
some voices

Despite AI acceleration, visible product improvements are lacking and fundamental OS/platform issues remain unresolved.

  • “While every post and thread feels like a 90's wall street office, the new android and iphone ship with fewer features than usual. No indie guys come up with a linux-sized alternative OS. Switch 2 remains unhacked. Windows takes 3 seconds…”

    torben-friis · Hacker News ↗

Linear Software development tool companyTuomas Linear CTOjulian_digital Linear engineer

Linear optimizes CI pipeline as AI agents accelerate code shipping
linear.app

How it unfolded 2 developments, newest first · click a bar or a number to jump articlespostscomments

Peak 7 pieces in one hour at Sep 21, 7 PM; 53 pieces over 3 days (2 articles · 5 posts · 46 comments) Sep 21, 2 PM — 4 pieces · 2 articles · 1 post · 1 comment — Newswires 2, Hacker News 2Sep 21, 3 PM — 3 pieces · 3 comments — Hacker News 3Sep 21, 4 PM — 2 pieces · 2 comments — Hacker News 2Sep 21, 5 PM — 4 pieces · 4 comments — Hacker News 4Sep 21, 6 PM — 3 pieces · 1 post · 2 comments — Hacker News 2, Mastodon 1Sep 21, 7 PM — 7 pieces · 7 comments — Hacker News 7Sep 21, 8 PM — 4 pieces · 4 comments — Hacker News 4Sep 21, 9 PM — 2 pieces · 2 comments — Hacker News 2Sep 21, 10 PM — 1 piece · 1 comment — Hacker News 1Sep 21, 11 PM — quietSep 22, 12 AM — quietSep 22, 1 AM — 1 piece · 1 post — Mastodon 1Sep 22, 2 AM — 2 pieces · 2 comments — Hacker News 2Sep 22, 3 AM — 3 pieces · 3 comments — Hacker News 3Sep 22, 4 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 5 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 6 AM — 1 piece · 1 post — Mastodon 1Sep 22, 7 AM — 2 pieces · 2 comments — Hacker News 2Sep 22, 8 AM — 3 pieces · 3 comments — Hacker News 3Sep 22, 9 AM — 2 pieces · 2 comments — Hacker News 2Sep 22, 10 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 11 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 12 PM — quietSep 22, 1 PM — quietSep 22, 2 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 3 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 4 PM — quietSep 22, 5 PM — quietSep 22, 6 PM — quietSep 22, 7 PM — quietSep 22, 8 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 9 PM — quietSep 22, 10 PM — quietSep 22, 11 PM — quietYesterday, 12 AM — quietYesterday, 1 AM — quietYesterday, 2 AM — 1 piece · 1 post — Mastodon 1Yesterday, 3 AM — quietYesterday, 4 AM — quietYesterday, 5 AM — quietYesterday, 6 AM — quietYesterday, 7 AM — quietYesterday, 8 AM — quietYesterday, 9 AM — quietYesterday, 10 AM — quietYesterday, 11 AM — 1 piece · 1 comment — Hacker News 1Yesterday, 12 PM — quietYesterday, 1 PM — quietYesterday, 2 PM — quietYesterday, 3 PM — quietYesterday, 4 PM — quietYesterday, 5 PM — quietYesterday, 6 PM — quietYesterday, 7 PM — quietYesterday, 8 PM — quietYesterday, 9 PM — quietYesterday, 10 PM — quietYesterday, 11 PM — quietToday, 12 AM — quietToday, 1 AM — quietToday, 2 AM — quiet 1–2
Sep 22yesterdaynow · 3:44 AM ET
  1. 2

    Companies report AI helping with tech debt and process automation, not just speed

    A commenter noted that their company's AI use is focused on burning down known technical debt and automating QA processes, allowing QA teams to shift from blockers to proactive reviews and deeper issue discovery.

    “A good chunk of what my company has been doing with AI falls into either burning down our known tech-debt and "easy wins" that no one ever had the bandwidth to approach... And improving / automating our processes.”
    — TrueDuality
    • because the tooling is struggling to catch up and adapt. there's still no vetted all-in-one solution that does code review, charts quality metrics, ingests incidents, and writes tests. there could be but each solution would necessarily need to be so bespoke to a codebase that you might as well hire some AI-pilled QAs and come up with it yourself…

      paimapiHacker News1d agoview on Hacker News ↗
    2 more of the top 3 · 40 posts in this stretch
    • A good chunk of what my company has been doing with AI falls into either burning down our known tech-debt and "easy wins" that no one ever had the bandwidth to approach... And improving / automating our processes. The former is having a direct and meaningful impact on the quality and availability of our services.Our QA, formerly a fairly frequent…

      TrueDualityHacker News2d agoview on Hacker News ↗
    • It's the difference between the value of "code" vs "software". Lots of people use those phrases interchangeably but its becoming painfully apparent that doesn't work anymore. Software requires more effort to actually make something IRL. Code can just be generated and sit in a repo, doing nothing, interacting with nothing.Github has reported a 14x…

      perrygeoHacker News1d agoview on Hacker News ↗
    all of them →
  2. 1

    Developer questions whether speed gains translate to product improvements

    A commenter raised skepticism about whether AI productivity gains are yielding visible improvements in shipped products, noting that new OS releases ship with fewer features than usual and foundational problems persist.

    “While every post and thread feels like a 90's wall street office, the new android and iphone ship with fewer features than usual. No indie guys come up with a linux-sized alternative OS.”
    — torben-friis
    • Here's my constant question:Everyone's going so fast that they keep hitting walls. Review, CI, product asking for things, whatever.Why have we not seen an improvements in products?While every post and thread feels like a 90's wall street office, the new android and iphone ship with fewer features than usual. No indie guys come up with a…

      torben-friisHacker News2d agoview on Hacker News ↗
    2 more of the top 3 · 6 posts in this stretch
    • > Moving our workloads off GitHub Actions to third-party runners with faster CPUs, higher-performance storage, and better cache infrastructure gave us faster machines to run the same pipeline onYeah, was not surprised to read this. Actions is convenient if you already use GitHub, but it can also be pretty slow. Given reliability is also a major…

      classictrafficHacker News2d agoview on Hacker News ↗
    • My take: it seems like systems should become smaller, more isolated, and contract-oriented.I have been a long time proponent of monoliths, but it seems like agents would be happier with smaller, more isolated services. The more isolated, the better. Contracts between the service components only. Then it can iterate internally as long as it…

      CharlieDigitalHacker News2d agoview on Hacker News ↗
    all of them →
  3. background

    Linear optimizes change-detection jobs by limiting fetch depth — The company capped fetch depth and removed unnecessary checkout operations from jobs that didn't need them, reducing the slowest change-detection gate from 94 seconds to 20 seconds.

  4. background

    Linear rewrites lint rules to eliminate TypeScript type dependency — Custom lint rules were refactored to use static analysis on the abstract syntax tree instead of building the full type graph, letting ESLint drop TypeScript entirely. This reduced API lint time by 68% and full-repository lint time by 55%.

  5. background

    Linear switches to native TypeScript compiler, cuts type-checking by 73% — Switching to tsgo, a native TypeScript compiler, cut the median weekly tsc check by 73%, moving the bottleneck off typechecking entirely.

  6. background

    Linear moves workloads off GitHub Actions to third-party runners — Moving CI workloads from GitHub Actions to third-party runners with faster CPUs and better cache infrastructure delivered a 34% average speed improvement, with some compiler checks like tsc dropping 52%.

  7. background

    Linear publishes CI optimization retrospective with measurable gains — Linear published a detailed account of its CI rework. Despite test suites nearly quadrupling since the start of the year, the company reduced pull request wait time from over 6 minutes to just over 5 minutes and cut runner time per test roughly in half.

  8. background

    Linear CTO assigns CI optimization task amid cost and speed concerns — Tuomas, Linear's CTO, assigned an engineer the issue "CI costs are high" and requested faster CI. The trigger reflected a broader shift: AI agents had made code shipping exponentially faster, but validation pipelines had not kept pace.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by HN Best, 2d ago · also HN Frontpage

What people are saying 18 voices from 1 site · best of 46 · verbatim

Still unanswered
  • If AI is making development so much faster, where are the tangible improvements in shipped products and user experience?
  • Why are companies able to accelerate code shipping but not seeing commensurate revenue growth?