Overview
What this challenge is about.
Read the module, the last 12 months of incidents touching it, and the existing tests. Write a 6-page specification using a precondition / postcondition / invariant format per public function. Add characterization tests until every existing branch is exercised, then refactor in 5-8 commits keeping the test suite green at every step. Measure cyclomatic complexity, line count, and PR turnaround time before and 4 weeks after merge. Deliver the spec document, the refactored module on a feature branch, and a 3-page before/after measurement report.
The Brief
What you'll do, and what you'll demonstrate.
Specify a critical 4,000-line payments module before refactoring it, and prove the refactor was safe with measurable metrics.
Earning criteria — what you'll demonstrate
- Write a precise specification using preconditions, postconditions, and invariants
- Use characterization tests to lock in legacy behavior before refactor
- Measure refactor success with concrete code-quality and flow metrics
- Sequence a refactor in small commits that stay green
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.