Table of Contents

🔄 Continuous Improvement Strategy¶

How this repository keeps getting better — during the six months and beyond.

Feedback loops (built into the cadence)¶

Daily: the "Mistakes Made" + "Knowledge Gaps" fields feed tomorrow's prep.
Weekly: the weekly review's Action Items and Weaknesses set next week's focus; re-quiz old topics (spaced repetition).
Monthly: the monthly review re-rates the skill matrix, picks "areas for improvement," and updates the portfolio.

Kaizen backlog¶

Keep a running list of repo improvements as GitHub issues labeled type: refactor / type: docs:

Promote dense journal notes → NOTES.md → cheatsheets/.
Refactor old project code as you learn better idioms (tag the commit refactor:).
Backfill tests/CI on early projects once you learn testing (Month 2+).
Add ADRs retroactively for past decisions worth documenting.

Revisit & re-derive¶

Every month, re-attempt one earlier exercise from scratch (no notes) to verify retention.
Re-read your Month-1 notes in Month-3 — fix anything now-known to be wrong (mark with a correction note, don't silently overwrite — the mistake is the lesson).

Quality ratchets (automation does the nagging)¶

CI must stay green; never merge red.
Resolve Dependabot PRs weekly.
Fix every markdown-lint / broken-link / spell-check finding promptly.

Measuring improvement¶

Track in PROGRESS.md: learning velocity (days/week), average confidence trend, exercises/week, and coverage on projects. The trend matters more than any single number.

After the six months¶

Convert the capstone into an ongoing maintained project (issues, releases).
Contribute to an open-source Go project (real-world review experience).
Teach: turn the best notes into blog posts or a short talk (learning-by-teaching).
Specialize: pick a depth track (distributed systems, performance, platform/K8s).
Re-run the interview bank quarterly to keep recall sharp.

⬅ README · Best-practices checklist