💻 Coding
Python Learning Sprint from Goals and Weekly Hours
Paste your Python goal, skills, weekly hours, and weak spots to get a 4-week sprint, drills, mini projects, and a mistake log without invented courses.
0Reviews
Prompt
Act as a Python coach who builds practice sprints from the learner's real goals and time budget, and who never invents course brands, certificates, or skills the learner did not claim. Inputs: - What you want to build or pass in the next 4 to 8 weeks: [Goal] - What you already know in Python (topics and comfort level): [CurrentSkills] - Weekly hours you can protect for practice: [WeeklyHours] - Topics or error types that keep blocking you: [WeakSpots] - Tools you already have installed (editor, OS, package manager): [Tools] - Whether you prefer notebooks, scripts, or both: [FormatPref] - A short sample of code or error you recently struggled with (optional): [SampleStruggle] Generate: 1. Four-week sprint outline: theme per week tied to Goal and WeakSpots, sized for WeeklyHours. 2. Daily practice blocks: 3 to 5 drills per week with exact file names and success checks. 3. Two mini projects that reuse CurrentSkills and stretch WeakSpots; list deliverables only from Goal. 4. Mistake-log template: columns for error text, cause guess, fix, and retest date. 5. Self-check quiz of 8 questions grounded in the week's topics (no answer key claims of official exam coverage). 6. Honesty note: list any library, course, or certificate not present in Inputs and therefore omitted. Rules: - Do not invent Udemy, Coursera, or bootcamp names unless the learner listed them. - Prefer the standard library and Tools the learner already has. - Output is a practice plan, not a degree or job guarantee.
Instructions
Paste your real goal, weak spots, and weekly hours. Run in ChatGPT, Claude, or Gemini. Follow the drills on your machine; do not treat the plan as a certificate or job promise.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Goal: automate CSV cleanup and write a small CLI that renames files by date for my photography folder.
CurrentSkills: variables, lists, for loops, basic functions; weak on pathlib and argparse; never used pytest.
WeeklyHours: 5 hours (Tue/Thu evenings 1.5h, Sat 2h).
WeakSpots: FileNotFoundError when paths have spaces; mixing str and Path; skipping tests.
Tools: macOS, VS Code, Python 3.12, pip.
FormatPref: scripts in a repo, not notebooks.
SampleStruggle: tried open('Photos/2024 trip/a.jpg') and got FileNotFoundError.Example Output
1. FOUR-WEEK SPRINT (5h/week)
Week 1 - Paths that survive spaces: pathlib.Path, Path.glob, quoting mental model. Cap: 5h.
Week 2 - CSV cleanup scripts: csv module, DictReader, writing cleaned rows. Cap: 5h.
Week 3 - CLI with argparse: rename-by-date dry-run flag. Cap: 5h.
Week 4 - pytest smoke tests + README for the CLI. Cap: 5h.
2. DAILY PRACTICE BLOCKS (Week 1 sample)
- Drill A (45m): create path_lab.py; list files under a folder whose name contains a space; success = prints count without FileNotFoundError.
- Drill B (45m): rewrite SampleStruggle using Path('Photos') / '2024 trip' / 'a.jpg'; success = open via Path.read_bytes on a fixture file you create.
- Drill C (30m): write path_quiz.md with 5 true/false claims about str vs Path; you answer without looking up docs first.
- Sat block (2h): combine A+B into list_photos.py that prints relative paths only.
3. MINI PROJECTS
- P1 CSV cleaner: clean_contacts.py reads messy.csv, strips whitespace, drops blank emails, writes cleaned.csv. Deliverable matches Goal CSV cleanup.
- P2 rename CLI: rename_by_date.py --dry-run scans a folder and prints proposed names YYYY-MM-DD_original.ext using pathlib + argparse. No cloud APIs.
4. MISTAKE-LOG TEMPLATE
| date | error text | my cause guess | fix tried | retest date | pass? |
| 2026-10-15 | FileNotFoundError ...2024 trip... | treated path as str with unescaped space | use Path parts | 2026-10-17 | |
5. SELF-CHECK (8)
1. Why does Path / 'a' / 'b' beat string join for nested folders?
2. What does Path.exists() return for a missing file?
3. Name one risk of open(user_input) without Path resolve checks.
4. When would you use Path.glob('*.jpg') vs rglob?
5. What does argparse dry-run usually print instead of writing?
6. Which csv reader gives column names as keys?
7. What is a minimal pytest file naming pattern?
8. How do you retest a FileNotFoundError after a fix?
6. HONESTY NOTE
Omitted: any paid course brand, Django/Flask, and pytest plugins not in Tools. Tools listed only macOS, VS Code, Python 3.12, pip.