PLECK lesson 90 · suggested week 18, day 5
Reflect and choose the next skill
Objective. Use evidence to set a specific programming growth goal.
Godot Engine Standard desktop editor 4.7.2-stable, GDScript (Godot 4), Compatibility renderer. Headless Godot 4.7.2.stable.official.ed1daf0bf passed 106 assertions on the supplied scaffolds, including malformed JSON saves. Audio used the Dummy driver and a synthetic WAV, not a speaker. The visual editor, browser export, and signed-in submission were not tested. The desk still does not run a student's own upload.
About 55 minutes. The due date is chosen by a parent.
Consent-based playtesting, repairs, evidence and reflection
Suggested pace: Recall and predict 5 min; Read instruction and scaffold 12 min; Build or design the assigned artifact 25 min; Run acceptance tests 8 min; Explain and checkpoint 5 min.
Materials: Paper and pencil or a private text document, Local course folder and prior checkpoint, No paid assets or public account required.
Comes after VGC-L089.
Reflection is a claim supported by evidence, not a list of compliments or apologies. Identify one design choice that improved task success, one code decision that simplified maintenance and one unresolved limitation. Cite the test or artifact supporting each. Then choose a next skill such as safer saves, clearer audio feedback or enemy state logic. Write a small measurable goal you could demonstrate in a later project. Keep the finished midyear version backed up before beginning new experiments.
Worked example
A report states candidate version, setup, action, expected result and actual result. A repair is verified by replaying exactly those steps, then checking neighboring features.
Reflect and choose the next skill — evidence task
- 1. Write a 200-word or two-minute private reflection with three evidence references.
- 2. Set one measurable next-skill goal and verify the final backup.
Deliverable. Midyear reflection and next-skill goal.
Acceptance checks
- VGC-L090-T1. Each claim points to a specific artifact or observation.
- VGC-L090-T2. The growth goal describes an observable outcome.
Understanding question. What makes “get better at coding” too vague as a growth goal?
Submit readable text or photos/scans of each numbered design page. Audio explanation may supplement a diagram or text, not replace requested artifacts.
If this is still shaky. Prioritize crashes, blocked completion and misleading controls before cosmetic feedback. Retest the original reproduction after each fix. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.
Optional extra. Explain one alternative implementation and why you chose the current one. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.
Turn in a typed answer, a JPEG, PNG, or WebP photo, a PDF scan, or an MP3, WAV, M4A, MP4, or WebM file up to 4 MB. A parent can log paper. One https address is stored as text and is not opened or run. Zip and code files are refused.
- Your first 2D game
Free public tutorial; no account; external asset download is optional, not used by this course.
· Opening this link does not submit the lesson.
This is a preview. A parent assigns the lesson and chooses the due date after the student is enrolled. The answer key is not on this page.