01 · The premise
A junior team doesn't become senior with a course. It becomes senior by watching someone experienced work on their code.
Technical coaching works when it's surgical: a senior who steps into real code, pairs on real tasks, writes reviews on real PRs. Not when it's one conference after another.
Our discipline is the XP practices that transmit best by osmosis: pair programming, collective code ownership, coding standards, continuous refactoring. You learn them by doing them with someone who has.
The Extreme Contract here is simple and hard: at the end the team must be autonomous. If our reviews stop at the end and quality collapses, we failed.
04 · The contract
Pre-conditions, post-conditions, invariants.
Every engagement has explicit pre-conditions, measurable post-conditions, and invariants we never violate. You know what we need at the start, what comes out at the end, and what we don't negotiate in the middle.
Pre-conditions / what we need from you
- Team open to coaching: they want to grow, not forced.
- At least one internal manager sponsoring the process (not enduring it).
- Access to repositories and review channels.
- Pair / review calendar agreed — no "whenever you have time".
Post-conditions / what we guarantee
- Measurable lift in code quality (review pass rate, test coverage, defect rate).
- Reduced onboarding time for new engineers.
- ADRs and living documentation maintained by the team without us.
- Postmortem culture established: incidents are analyzed, not hidden.