28 - Levels 0 to 2 Deep Guide (Beginner to Competent)¶
Home: README
Path placeholder: <repo-root> means the folder containing this repository's README.md.
This guide is your exact execution protocol for levels 0, 1, and 2.
Objective¶
Turn a beginner into a consistent builder of small, reliable Python tools.
Required inputs¶
Standard run pattern (copy/paste)¶
cd <repo-root>/projects/level-0/01-terminal-hello-lab
python project.py --input data/sample_input.txt --output data/output_summary.json
pytest -q
Expected output:
Per-project sequence (do not skip steps)¶
- Read project README first.
- Run baseline script.
- Run tests.
- Read
project.pytop to bottom. - Do one "alter" change.
- Do one "break" change.
- Fix and verify.
- Record root cause notes.
Break/fix drill examples¶
Choose one per project: 1. Remove or rename a required input line and verify safe handling. 2. Change a condition and verify tests catch bad behavior. 3. Change output key names and verify tests fail then fix correctly.
Weekly completion target¶
- Minimum: 3 projects/week.
- Recommended: 5 projects/week.
- Accelerated: 7+ projects/week.
Learning-style options (Play/Build/Dissect/Teach-back)¶
- Play: mutate constants and inputs and observe output changes.
- Build: run every step in this doc exactly.
- Dissect: rewrite one project with simpler variable names and comments.
- Teach-back: explain one finished project in 5 minutes to notes/voice.
Knowledge checkpoints¶
By end of level 0: - variables, strings, input/output, loops, files.
By end of level 1: - conditionals, dictionaries, validation, parsing.
By end of level 2: - transforms, retries, small pipeline reasoning.
Exit gate (must pass before level 3)¶
- You can explain any line in one level-2
project.py. - You can add one new test and keep all tests green.
- You can induce one failure and recover in under 20 minutes.
- You can explain why your fix is correct.