#CI
6 pieces filed under “CI”.
Build times are a team-health metric
Build time as a team-health metric: profiling CI honestly, cache strategies, test sharding, and the cultural rules that keep pipelines under five minutes.
Bundle budgets: the 170kb rule and how we hold it
Our rule: 170kb of compressed JavaScript per route, or the PR explains itself. How the budget works and where we spend bytes on purpose.
Accessibility is an engineering discipline, not a ticket queue
Treating accessibility as infrastructure: axe in CI, linting, component contracts, keyboard hierarchies, and who on the squad owns what. WCAG AA as a floor.
Testing design tokens in CI like the API they are
Design tokens are an API contract between design and engineering. The CI pipeline that enforces it: grammar linting, ancestry checks, contrast tests.
The technical SEO checklist we run before every launch
Our pre-launch SEO checklist became code: crawl assertions in CI, header diffs, structured-data audits — plus the judgement checks that never automate.
A testing strategy that ships: what to test, what to skip, what to delete
Our testing pyramid, rebuilt for reality: contract-first unit tests, a thin layer of Playwright journeys, flake budgets, and a CI bill we defend monthly.