Building a Personal FDE Learning Plan That You'll Actually Finish
Updated · Tech checked
Effective plans reverse-engineer from target role evidence: pick the gaps from a readiness assessment, schedule 4-6 weekly hours with a project each month, and measure by shipped artifacts - not modules watched.
The short answer
Plans fail when they list topics instead of scheduling artifacts. Reverse-engineer: target role → evidence the role demands → your gaps → one project per month that closes a gap. Four to six hours weekly, defended like meetings.
Step 1 - Baseline honestly
Take a structured assessment (ours: the free readiness check) or score yourself 1-5 against the skills matrix: engineering craft, discovery, data/integration, AI judgment, communication. No self-flattery; the plan's quality depends on this.
Step 2 - Pick two gaps, not five
Two gaps × one project each per month beats a sprawling curriculum. Depth compounds; coverage decays.
Step 3 - The monthly project pattern
| Month | Project (artifact) | Gap closed |
|---|---|---|
| 1 | Integration with reconciliation + error report | data/integration |
| 2 | Retrieval assistant with ACL + eval table | AI judgment |
| 3 | Discovery role-plays ×6 + two written briefs | discovery |
| 4 | Productionized deployment with runbook + rollback | operations |
Each project follows the portfolio format so output accumulates into job evidence automatically.
Step 4 - Cadence and review
- Weekly: 2×2h deep blocks + 1-2h review of a guide on the current gap.
- Biweekly: one mock discovery call or trade-off presentation recorded.
- Monthly: ship the artifact, self-score against the relevant rubric, adjust next month.
Anti-patterns
- Course-hopping (three providers, zero projects).
- "I'll network after I'm ready" - share artifacts as you build; feedback is curriculum.
- Plans without dates. "This quarter" is not a date.
Continue: Roadmap · Practice tasks