CurriculumWeek 04 · Capstone
Week 04 · starts Jun 08
Capstone
Extend one of your projects into something portfolio-ready. Push it to GitHub. Present on Friday.
Upcoming
Sessions
- 04.01Project planning and code organization~24 min readOpen →Breaking a project into steps. Splitting code across files. Writing function names you'll still understand in a week.~24 min readOpen →
- 04.02Build block + GitHub~20 min readOpen →Just enough git to publish: init, add, commit, push. Then a real README in markdown.~20 min readOpen →
- 04.03Demo day~10 min readOpen →Three to five minutes each. What it does. What you learned. What you'd add next. Cohort gives feedback.~10 min readOpen →
Practice exercises for this week
short · graded
- wk04.p1One-page plan for your capstone~30–45 minView →Before you write a single line of capstone code, write the plan on one page. Problem, user, inputs, outputs, files, functions.~30–45 minView →
- wk04.p3Rehearse your demo on camera~45–60 minView →Write a three-minute script for your capstone demo, record one take of yourself reading it, and watch it back. The point is to feel the awkward, not avoid it.~45–60 minView →
- wk04.p2Publish a tiny repo to GitHub~30–45 minView →Create a public repo with one Python file and a README. The point is not the code — the point is finishing the publish loop end to end.~30–45 minView →
Assignment for this week
Capstone — your portfolio project
Extend one of your week's projects (or pick from the menu) into a polished, GitHub-published, README-having project you can show off.
Due Fri, Jun 12 · Demo Day
Read brief →Demo Day Jun 12