Everything so far, and your first architecture question
By the end of today you can connect the eleven days behind you into one picture, identify which two concepts you are weakest on, and answer a design question about where code should live and why.
YesterdayDays 1 to 11 covered how code runs, what values are, control flow, functions, collections, errors, debugging, the shell, environments, git, and reading code.
TomorrowTomorrow begins Phase 2, where you start asking not just whether code works but what it costs.
Why this matters
Consolidation is where scattered facts become a model you can reason with. It is also the first time you are asked a question with no single correct answer, which is what engineering mostly is.
- Separation of concerns
- Questions to ask of code
- Choosing a collection
- Why we split code
Learn it
70 minCopy this into Claude or ChatGPT. It quizzes you before it explains anything, which is deliberate. The resources under it are how you check what it told you.
Today's Master Prompt
Free · sign inA prompt written for this day alone: your level, the exact scope, what to leave out, and an instruction to quiz you before it explains anything. Paste it into Claude or ChatGPT and it teaches you today's material.
Check it against something that is not a model
An assistant can be fluent and wrong, and on a topic you met today you will not catch it. These cover the same ground and were made by people who do this for a living, so they are what you hold the explanation up against. They are other people's work and we only link to them, so judge them for yourself.
3 hand-picked resources
Free · sign inVideos, official docs and articles covering the same ground, each opened and annotated by hand. They are what you check the assistant against on a day you cannot yet catch it being wrong.
Build it
45 minTake the 60-line script from today's session and split it the way you argued for. Then write two sentences on what got better and one on what got worse. There is no correct split; the reasoning is the exercise.
Recall it
25 minAnswer out loud, reveal, then mark honestly whether you had it. That score is the only thing on this page you do not get to choose.
5 recall questions
Free · sign inQuestions you answer from memory, then grade yourself against the real answer. The score is carried into the mastery rating below it, so an honest miss cannot quietly become a tick.
Rate it
Completion and mastery are tracked separately. Be honest, because an inflated rating only means the concept resurfaces sooner.
Mastery tracking
Free · sign inRate yourself against five named criteria per concept. Completion and mastery are tracked separately, and anything you rate shakily comes back automatically on a spaced schedule.
Recap
- 01Everything since Day 1 is one chain: memory, names, logic, boundaries, failure
- 02You now have a method for reading code and a method for debugging it
- 03The weakest two concepts today are the ones the review queue will bring back
- 04Architecture questions have no single answer, only defensible ones
Your progress
Free · sign inMark days complete, pick up where you left off across devices, and watch completion and mastery diverge. Free, and the account exists only so ninety days of work cannot vanish with a cleared browser.