21 points julian_digital 53 minutes ago 8 comments

azkalam 33 minutes ago | parent

If you can pay the setup cost, Bazel will get you build times ~10s with a warm cache for even massive projects.

d_sc 26 minutes ago | parent

vitest load balancing on test duration times instead of by file would be a nice performance win

moofeez 6 minutes ago | parent

We actually tried this and (for us) it doesn't lead to enough of a gain that's worth the extra complexity.

mraza007 19 minutes ago | parent

Agentic Coding has been a huge strain on CI, I have been using Bazel to improve our build times and ultimately building customized runners to improve our CI

Anyways great blog post from linear team a lot to learn from it

alexnewman 17 minutes ago | parent

My recent winnowwallet.com still has build times of over 10 minutes. I'm convinced the agent really wants build times around 5m to move at a quick pace. Also to not drive me insane. It took a ton of work to get it down from 45 minutes because my tests launch a full version of the app, and walk it through major usecases while recording video and screenshots. I then use AI to qa this. It also generates its webpage this way. All from CI/CD

xracy 11 minutes ago | parent

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.

bognition 9 minutes ago | parent

CI -> Continuous Integration

Its best thought of as the testing systems that are run as part of pull request review / merge to main / build processes.

handfuloflight 9 minutes ago | parent

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 "I am in tech" means "I am a software engineer", and you don't know what CI is, then boy; I'd be worried for you.