- Published on
Rework Build speed: what I learned (039)
Jigar Patel
2 min read
I used this as a focused experiment, and I wrote it down while it was still fresh.
Why I touched it
I forced myself to stop and write the failure mode before touching code.
I kept everything practical by using a short loop around Build speed.
Implementation notes
I started with a narrow goal: keep the same behavior, reduce one risk, and keep rollback trivial. I moved from vague ideas to explicit rules before touching production paths.
Validation checklist
- Capture real inputs
- Check timeout behavior
- Track latency before and after
- Add follow-up reminder
Snippet
set -euo pipefail
node --version
npm ci
npm run lint
npm run test
I also ran this while working from a family dinner prep for one IRL pass.
What I kept
- This build speed setup now has a measurable improved mean time to fix path.
- I keep the same format for every future run.
- If it can be explained in one checklist, it usually scales better.