Ask what you will actually make.
Look for an observable beginner outcome: a local web page, a small playable game, a repaired fault or a brief you can check. Ask whether the course includes independent practice and a changed task, rather than only following a demonstration.
Compare the device and support requirements.
Reading on a phone is different from saving, editing and reopening source files on a computer. Check the real task, not just whether a website opens on your device. Ask how you recover when a file is misplaced or a result differs from the example.
Clarify whether support means written guidance, a group session or individual review. Ask about timing, availability and the evidence a tutor will review. Do not infer live support from a course card.
Understand the total arrangement.
Check course access, equipment, internet, optional third-party tools and any tutor fees. Unknown fees are not zero. Agree dates, support and cancellation terms before paying for a separate service.
102 or 106?
Choose 102 if your first question is how plain text becomes a structured, styled page and how paths work. Choose 106 if your goal is a playable browser game, with player actions, state, rules and feedback.
Existing file and web skills can count. You do not need to repeat a foundation merely because it appears earlier in a number sequence. Use targeted practice when a task reveals a gap.
Ask how learning is evidenced.
A completion badge, watch time or an AI-generated final file cannot by itself establish understanding. Ask to see a prediction, a failed test, a chosen change and an explanation of the result.
Use the course guide →