Build a Week-by-Week Coding Practice Plan with Mini-Projects

Get a week-by-week plan for learning a programming language, fitted to your level and hours, where each week ends with a small project and a checkable definition of done.

You getOne-line summary of the plan, table and for each week

Prompt

Prompt
You are a senior software engineer who mentors self-taught programmers.

Your job: build a week-by-week practice plan for learning a programming language. Before writing the plan, ask me these questions in one numbered message, then wait for my answers:
1. Which language do you want to learn, and why (job, hobby, school)?
2. What is your current level: total beginner, know another language, or know some of this one?
3. How many hours per week can you practice, and for how many weeks?
4. What kind of program do you want to be able to build by the end?

Rules:
- Each week fits inside my stated hours, with hours shown for every task.
- Each week introduces at most 3 new concepts, named plainly.
- Each week ends with a small project that has a Definition of done of 3-5 checkable items (e.g. 'handles empty input without crashing').
- Every project reuses at least one concept from an earlier week.
- Suggest resources by type only (official docs, interactive exercises). Do not invent links or course names.

Output format:
1. One-line summary of the plan.
2. Table: Week | New concepts | Practice tasks (hours) | Mini-project
3. For each week: a 2-sentence project brief and its Definition of done checklist.
4. If you fall behind: what to cut first.

End with one line listing the assumptions you made and what I could tell you to sharpen the plan.

Example output

At a glanceSix-week Python plan with weekly mini-projects5 hours per week, from first print statement to a CSV summary script
  1. Tip calculatorWeek 1Variables, input/print, numbers vs strings
  2. Grade checkerWeek 2If/else, comparisons
  3. Shopping list totalerWeek 3Lists, for loops
  4. Unit converter menuWeek 4Functions, return values
  5. Contact list cleanerWeek 5Reading/writing files, CSV module
  6. Expense summary reportWeek 6Dictionaries, basic error handling

Example for: an office administrator learning Python from scratch, 5 hours/week for 6 weeks, wants to automate spreadsheet chores.

Plan: Six weeks from first print statement to a script that cleans and summarizes a CSV export.

WeekNew conceptsPractice tasks (hours)Mini-project
1Variables, input/print, numbers vs stringsInstall Python + editor (1), exercises (3), project (1)Tip calculator
2If/else, comparisonsExercises (3), project (2)Grade checker
3Lists, for loopsExercises (3), project (2)Shopping list totaler
4Functions, return valuesRefactor weeks 1-3 (2), project (3)Unit converter menu
5Reading/writing files, CSV moduleOfficial docs reading (1), exercises (2), project (2)Contact list cleaner
6Dictionaries, basic error handlingExercises (2), final project (3)Expense summary report

Week 1 – Tip calculator. Ask for a bill amount and tip percentage, then print the tip and total.

  • [ ] Accepts decimal amounts like 42.50
  • [ ] Prints total rounded to 2 decimals
  • [ ] Runs start to finish without errors

Week 2 – Grade checker. Takes a score 0-100 and prints a letter grade, reusing input handling from Week 1.

  • [ ] Correct letter for 5 test scores you pick
  • [ ] Prints a message for scores outside 0-100
  • [ ] No duplicated if-blocks

Week 3 – Shopping list totaler. Collect item prices until the user types 'done', then show count and total.

  • [ ] Stops cleanly on 'done'
  • [ ] Shows item count and total
  • [ ] Works with an empty list (total 0)

Week 4 – Unit converter menu. A menu offering 3 conversions, each written as its own function.

  • [ ] At least 3 functions with return values
  • [ ] Menu loops until the user quits
  • [ ] Invalid menu choice shows a message, not a crash

Week 5 – Contact list cleaner. Read a messy CSV of names and emails, trim spaces, lowercase emails, write a clean file.

  • [ ] Output file has the same row count as input
  • [ ] No leading or trailing spaces remain
  • [ ] Blank rows are skipped

Week 6 – Expense summary report. Read an expenses CSV and print totals per category, sorted highest first.

  • [ ] Uses a dictionary for category totals
  • [ ] Skips rows with non-numeric amounts and reports how many
  • [ ] Output matches a hand-checked total for a 10-row sample

If you fall behind: Drop the Week 4 refactor first, then merge Weeks 2 and 3 exercises. Keep every mini-project; they are the real practice.

Assumptions: you're on Windows or Mac with admin rights to install Python, and your spreadsheets can be exported as CSV. Tell me your real file layout to tailor Weeks 5-6.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking level, hours and goal first means the plan fits your real schedule instead of a generic 12-week course.
  • A 3-5 item Definition of done turns each project into something you can verify, so you know when a week is finished.
  • Capping new concepts at 3 per week and reusing earlier ones prevents overload and builds retention.

Use this in ChatGPT, Claude or Gemini when starting a new language. Know your weekly hours, your current level, and one thing you'd like to build by the end.

Common edits

  • Ask for daily breakdowns instead of weekly totals if you practice in short sessions.
  • Add 'include one debugging exercise per week' to build troubleshooting skills.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Coding