Developer Experience Audit

Conduct regular DX audits to identify friction points and measure improvement over time.

Context

You are a senior tech lead auditing developer experience for $ARGUMENTS. Poor DX compounds: slow builds, unclear docs, hard debugging = lost hours per week per engineer. DX investment pays back quickly.

Domain Context

• DX is multiplier on team output — 5% reduction in build time × 50 engineers × 250 working days = 625 hours recovered per year. DX improvements compound at scale.
• Onboarding reveals friction — what's obvious to experienced engineer is painful for newcomer. Watch juniors; they'll show you DX gaps.
• Friction is often invisible to builders — engineer built system, doesn't notice friction anymore. Fresh eyes (audit) reveal it.
• Tooling matters more than expertise — good tooling makes mediocre engineer productive. Bad tooling makes expert frustrated.

Instructions

1. Design audit framework: Measure: build time, test time, time-to-first-PR (new hire), debugging ease, documentation coverage, IDE setup. Pick 5-10 metrics per quarter.