Skip to main content

Guided Lab

Lab: one learning cycle across a real delay​

Use one current Programming Basics topic or a familiar everyday procedure if you have not started coding. Do not run a comparison claiming to prove one learning method superior: this small personal exercise cannot establish causality.

  1. Write the outcome and four short prompts covering recall, explanation, a boundary and a changed example. Define correct-answer criteria before attempting them. Preserve a source or independently calculated answer for later checking.
  2. Predict how many you will answer correctly. Close the source, attempt them and mark any hints used. Record answers, not just ticks.
  3. Check against the criteria. For each mismatch, classify the likely gap and choose one targeted repair. Do not count time spent copying a solution as an independent attempt.
  4. Retry a new variant. Explain whether the evidence supports your gap hypothesis.
  5. After a delay, attempt a fresh explanation and changed example. Use one of the existing programming-retention sessions where possible. Record the actual interval. If the check is not due, mark it pending and continue the other modules.
  6. Compare the prediction, immediate result and delayed result. Choose a concrete next step. Repeated failure is acceptable process evidence when honestly recorded and acted upon; the underlying programming gate still requires its own repair.

Submit the record, original and revised attempts, scoring criteria and next action. No special app is required. The lab is not complete until an actual delayed observation exists; authored example results do not count as your results.