How we cut build times in half without changing the stack

Every team hits the wall where the build is the slowest part of the day. Ours crept past eleven minutes before anyone noticed it had become the tax on every change we shipped.

We did not rewrite anything. We measured, found the three slow stages, and cached the parts that never changed between runs. The result was a build that finished in under five minutes.

Start by measuring, not guessing

The first move was the least glamorous: instrument the pipeline so each stage reported its own wall-clock time. The numbers contradicted everyone's hunch about where the time went.

The slowest stage was never the one people complained about.

Once the data was honest, the fixes were obvious and small. Cache the dependency install, reuse the compiled output, and stop doing the same work twice on every push.