← All insights
CI/CD that teams actually keep using
A pipeline nobody trusts gets bypassed. Build one that sticks.
The pipeline that gets ignored
Plenty of teams have CI/CD on paper and deploy by hand anyway. Usually it's because the pipeline is slow, flaky, or opaque.
Make it fast
Cache dependencies, run tests in parallel, and keep the critical path under ten minutes. Speed is a feature.
Make it trustworthy
Flaky tests erode trust faster than anything. Quarantine them, fix them, and keep the signal clean.
Make it reversible
A one-command rollback turns deploys from scary to routine. That single property changes a team's whole relationship with shipping.
Get new insights by email
Occasional, practical notes on civic tech, security, and building dependable software. No spam, unsubscribe anytime.
Related reading
Engineering5 min read
How to choose a software partner (without being technical)
A short, honest guide for non-technical founders evaluating who to build with.
ConsultingBusiness