B: a confident first step into programming
Start here if: you have not written software before. Budget: 40 weeks × 12 hours = 480 hours: a 12-week on-ramp (144 hours) followed by A's 28 weeks (336 hours).
Begin with ordinary programs you can understand, debug and test. No paid exam, model training or cloud subscription is needed for the on-ramp. Each week: about 6 hours learning, 5 practice and 1 explaining/reviewing.
Your first 12 weeks
The CS50P lessons below include lecture materials and problem-set links. Complete their assessed work according to the provider's rules if seeking course completion. The project exercises in the final column are additional practice, not replacements for those requirements.
| Week | Open and study | Try it and save the result |
|---|---|---|
| 1 | CS50P: Functions, Variables | Write a small question/topic input program; explain each function and value. |
| 2 | Conditionals and Loops | Process a list of questions; handle an empty list and unexpected input. |
| 3 | Exceptions and Libraries | Catch invalid values, use a library and inspect one API response. |
| 4 | Unit Tests and File I/O | Read/write CSV; test a missing file and a malformed record. Rebuild one function without copying. |
| 5 | Regular Expressions | Validate a simple identifier; explain where plain string checks are easier. |
| 6 | Object-Oriented Programming and Et Cetera | Model one question as an object; add a command-line argument and explain the design. |
| 7 | CS50P final project | Plan and implement a small question organizer; follow the current function/test requirements. |
| 8 | CS50P final project and course overview | Finish missing problem sets and the project. Gate B1: independently explain files, exceptions and tests. |
| 9 | CS50 SQL: Querying | Load a small dataset; write filtering, ordering and aggregate queries. |
| 10 | Relating and Designing | Join questions to topics; define keys and constraints, then test invalid data. |
| 11 | Upstream Git and Collaboration and uv projects | Version a change, exclude secrets/generated files and reproduce the environment. Practice locally before sharing. |
| 12 | Revisit Libraries/API material and A's entry check | Add a timeout and failed-response handling; reproduce a bug with a test. Gate B2: pass A's entry check independently. |
CS50P contains ten instructional weeks plus a final project. This plan groups some topics into eight study weeks; it is not the provider's promised pace. Extend it whenever lectures, exercises or the project need more time. Selected SQL lessons are not completion of CS50 SQL.
Continue the same project through A
| B calendar | Follow | Completion evidence |
|---|---|---|
| 13–16 | A, phase 1 | Tested API/database service and reproducible setup |
| 17–24 | A, phase 2 | Baseline, held-out evaluation and explained model errors |
| 25–30 | A, phases 3–4 | Structured feature, grounded answers and retrieval evaluation |
| 31–38 | A, phases 5–6 | Bounded tools, sandbox delivery, monitoring and recovery |
| 39–40 | A, phase 7 | Clear case studies and independent review |
Do not restart the project or buy a new course at every phase. Keep a small bug journal: what you expected, what happened, how you tested the fix.
Course certificates recognize the provider's completion conditions, not a degree or professional experience. See courses and credentials; optional exams come after practical gates, not before them.