Overview
What this challenge is about.
Read the class + git blame to map its responsibilities. Write characterization tests (using approval testing) until you can change behaviour without surprise — target at least 75 percent line coverage of the public surface. Apply the Mikado method: pick a target end state, attempt it, revert and write down what blocks it, repeat until you have a directed graph of safe steps. Execute the graph leaf-first. Deliver the refactored class (or a strangler-pattern replacement), the characterization test suite, the Mikado graph, and a 5-page case study for the team's internal wiki.
The Brief
What you'll do, and what you'll demonstrate.
Refactor a 4,000-line reckless-inadvertent debt hotspot incrementally over 4 weeks without freezing the team's feature work.
Earning criteria — what you'll demonstrate
- Apply the Mikado method to a real legacy refactor under feature-work pressure
- Use characterization tests to refactor behaviour-preserving code safely
- Decide when to refactor in-place vs use the strangler pattern
- Document a refactor so other engineers can learn the technique
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.