What next
Before anyone relies on it#
- Handle the errors you skipped. A tutorial leaves these out deliberately; a real thing cannot.
- Know when it breaks. Even a weekly check by a human beats finding out from a user.
- Write down how to run it again. Three months from now you will not remember, and the person who asks might be you.
Extensions worth trying#
Fill this in: three or four, ordered from an evening to a weekend, each naming what it teaches rather than what it adds. "Add caching" is a task; "see what changes when the answer can be stale" is a reason.
Reading that actually helps next#
Point at the official documentation for the specific parts this series touched, not at the front page of it. A reader who just finished a tutorial can absorb a reference page on one subject and will bounce off an entire manual.
The most useful thing you can do this week is rebuild it from memory, without the tutorial open. It takes half the time and teaches roughly twice as much, because the parts you cannot recall are exactly the parts you did not learn.