Teach, demonstrate and record
20 prepared demonstrations. Each is planned for 3–7 minutes; rehearse to fit your audience. Open the prepared screen directly, follow the script and use actual output as evidence. Print this page for classroom notes.
Demo 1 · What JavaScript is and what you can build with it
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title What JavaScript is and what you can build with it and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Hello, JavaScript!
Teaching explanation: JavaScript is a language for giving a computer precise instructions. A website uses HTML for content, CSS for appearance and JavaScript for behavior. Your first instruction displays a message in a console, a place where a program can report what happened. You do not need any previous programming experience. The message is source code written as a string: text surrounded by quotation marks. Changing the text changes the displayed result, not the meaning of console.log.
Closing: What would you change next, and what result would prove that it works?
Demo 2 · Understanding variables as containers for information
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding variables as containers for information and prepared source.
- Predict: Ask: What changes when you run the instructions in this order?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: 5
Teaching explanation: A variable associates a name with a value. The familiar container diagram is a learning metaphor, not a picture of engine memory. Reading the name uses its current value. In this program score starts with a number and is then displayed. The identifier is not part of the output unless you put it inside a string. Good names let you understand what a value represents before studying every calculation.
Closing: What would you change next, and what result would prove that it works?
Demo 3 · Understanding strings
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding strings and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Message: Hello
Teaching explanation: A string represents text. Quotation marks delimit the text in source code and are not themselves printed. Spaces inside a string are part of its value. The plus operator joins strings, so this example puts a greeting before a supplied name. A number written inside quotation marks is text too, which matters when you later perform arithmetic. Choose one quote style consistently and escape any matching quote used inside it.
Closing: What would you change next, and what result would prove that it works?
Demo 4 · Basic arithmetic operations
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Basic arithmetic operations and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: 8
Teaching explanation: Arithmetic expressions combine numeric operands and an operator. Addition uses +, subtraction uses -, multiplication uses *, and division uses /. JavaScript evaluates the expression and produces a value that can be stored or displayed. This receipt calculation subtracts a discount from an initial amount. A program cannot infer which numbers are prices, percentages or quantities: that meaning comes from your design and readable names.
Closing: What would you change next, and what result would prove that it works?
Demo 5 · Creating and combining strings
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Creating and combining strings and prepared source.
- Predict: Ask: What changes when you run the instructions in this order?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Welcome, Alex!
Teaching explanation: Concatenation joins strings without inserting separators automatically. You must include each desired space and punctuation mark. A string can be stored once and reused in a larger message. The computer does not know that two words should be separated, so compare the exact characters in the expected output. This is useful for labels and greetings, though template literals soon make longer messages easier to read.
Closing: What would you change next, and what result would prove that it works?
Demo 6 · Comparison operators
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Comparison operators and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: true
Teaching explanation: A comparison asks a question and produces true or false. The greater-than operator excludes equality, while greater-than-or-equal includes it. Choosing the boundary correctly matters for minimum ages, stock thresholds and scores. A comparison does not change the compared value. Write down the expected result at exactly the threshold as well as on each side.
Closing: What would you change next, and what result would prove that it works?
Demo 7 · Understanding repetition and loops
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding repetition and loops and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: 0 1 2
Teaching explanation: A loop repeats a set of instructions while a condition remains true. The repeated body should make progress toward stopping. A simple counter lets you see exactly which iteration is running. Loops are useful for repeated work, not merely printing numbers. They can also hang a program if the stopping condition is never reached, so our worker has a strict execution limit.
Closing: What would you change next, and what result would prove that it works?
Demo 8 · Understanding what functions do
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding what functions do and prepared source.
- Predict: Ask: What changes when you run the instructions in this order?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Hello, Alex
Teaching explanation: A function groups instructions under a name so you can reuse them. Defining a function does not execute its body. Calling it with parentheses runs the body, and return gives a result back to the caller. console.log then displays that returned value. Start with one responsibility and a name that describes the action. The three examples call the same function with different arguments, so the reusable rule stays separate from the data.
Closing: What would you change next, and what result would prove that it works?
Demo 9 · Understanding the call stack
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding the call stack and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: 7
Teaching explanation: The call stack tracks active function calls. When solve calls double, solve pauses until double returns. The returned number then participates in the remaining addition. A stack diagram is a conceptual picture of this call order, not a full debugger for all JavaScript engines. Small named helpers make intermediate responsibilities visible and allow focused tests.
Closing: What would you change next, and what result would prove that it works?
Demo 10 · Creating and understanding arrays
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Creating and understanding arrays and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: 0
Teaching explanation: An array is an ordered collection written with square brackets and comma-separated values. The literal in each function call creates the collection. Array length reports its number of positions, and index zero accesses the first element. This helper returns an explicit null for an empty array before trying an indexed read. The empty-array guard is a policy we wrote, not a general rule that all invalid indexes return null. Arrays are objects, but their ordered positions make them useful for lists.
Closing: What would you change next, and what result would prove that it works?
Demo 11 · Transforming data with map()
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Transforming data with map() and prepared source.
- Predict: Ask: What changes when you run the instructions in this order?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: [3,6]
Teaching explanation: map creates one output element for every visited input element. Use it when you want a transformation, not when you want to remove items. A return value inside the callback becomes an element of the resulting array. map calls a callback for each input element and collects the returned values without changing the array length.
Closing: What would you change next, and what result would prove that it works?
Demo 12 · Understanding JavaScript objects
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding JavaScript objects and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Alex
Teaching explanation: An object groups named properties inside braces. In the literal {name: "Alex"}, name is a property key and "Alex" is its value. A colon connects them; commas separate additional properties. Dot notation reads a known property name, so person.name uses the name property rather than an array position. An object’s braces describe data, while a function’s braces describe a block of instructions. Empty text is still a present property value. Nested objects and dynamic keys follow in later lessons.
Closing: What would you change next, and what result would prove that it works?
Demo 13 · Understanding the Document Object Model
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding the Document Object Model and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Run the preview tests; inspect the live page.
Teaching explanation: A DOM tree contains more than elements. Text inside an element is represented by a text node. children lists element children; childNodes includes text and comments too. Whitespace between tags may therefore change a childNodes count. Use the collection that matches your intent rather than assuming every node is an element. This fixture deliberately includes a text node followed by a strong element. The document is a tree of element and text nodes. Inspect the live tree after running a change.
Closing: What would you change next, and what result would prove that it works?
Demo 14 · Understanding browser events
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding browser events and prepared source.
- Predict: Ask: What changes when you run the instructions in this order?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Run the preview tests; inspect the live page.
Teaching explanation: addEventListener connects an event type with a callback. Pass the callback function rather than the result of calling it. The function runs later when the event occurs. A native button already supports keyboard activation, so it is a better starting point than making a clickable div. Keep visible feedback close to the action and meaningful to the user. An event listener registers behavior for later. Adding the listener does not immediately execute its handler.
Closing: What would you change next, and what result would prove that it works?
Demo 15 · Handling forms and user submissions
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Handling forms and user submissions and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Run the preview tests; inspect the live page.
Teaching explanation: A form submit event represents the form-level action, including keyboard submission. Listen on the form rather than only a button click. preventDefault lets a demo handle submission without navigating. In a real application you still need appropriate server validation and an actual save or send operation. This lesson only updates an on-page status; it sends nothing. A submit handler can prevent the browser navigation and handle the form locally. Native validation still has a useful role.
Closing: What would you change next, and what result would prove that it works?
Demo 16 · Saving information with localStorage
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Saving information with localStorage and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: Use the preview controls and compare the named behavior checks.
Teaching explanation: This complete example connects state, form submission, rendering and browser persistence. The source owns a project-specific storage key. On startup it parses saved data inside try/catch and validates required record fields. User actions change records, save the serialized collection and render a view using textContent. A storage failure is reported without pretending the data was saved. The sandbox provides an in-memory localStorage adapter; export the project and serve it over HTTP to verify real reload persistence. Browser storage belongs to an origin and is not a secure vault.
Closing: What would you change next, and what result would prove that it works?
Demo 17 · Understanding syntax, runtime, and logic errors
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding syntax, runtime, and logic errors and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: {"a":1}
Teaching explanation: JSON.parse can throw when text is not valid JSON. A targeted try/catch lets you return a controlled fallback. Do not label a fallback as successfully restored data; callers should know whether parsing worked when that distinction matters. Syntax errors prevent parsing; runtime errors occur during execution; logic errors run but produce the wrong result. This example catches a runtime parse error.
Closing: What would you change next, and what result would prove that it works?
Demo 18 · Understanding the event loop, tasks, and microtasks
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Understanding the event loop, tasks, and microtasks and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: A D C B
Teaching explanation: The event loop coordinates tasks and microtasks while ordinary code still runs synchronously within the current task. The classic prepared example prints A, D, C, B. A zero-delay timer does not interrupt the current task. The already-resolved promise schedules its then callback for a microtask checkpoint before the timer task runs. Our worker captures actual console order; queue diagrams are simplified educational models and do not inspect hidden engine queues.
Closing: What would you change next, and what result would prove that it works?
Demo 19 · Retrieving information using fetch()
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Retrieving information using fetch() and prepared source.
- Predict: Ask: What changes when you change the value but keep the operation?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: JavaScript Discovery
Teaching explanation: fetch normally performs a request and returns a promise for a Response. To make this exercise reproducible without network access, fixtureFetch is an explicitly supplied local adapter with the same small response-reading interface. It is not a real server request. The code awaits the response, then awaits its JSON body. In production, use a permitted URL and check response.ok before reading usable data.
Closing: What would you change next, and what result would prove that it works?
Demo 20 · Building responsibly with AI-assisted coding
Open prepared demonstration · Printable lesson
Opening narration: What do you think this program will do? Today we will test the prediction instead of trusting a guess.
- Open prepared demo: Use the direct link. Confirm the title Building responsibly with AI-assisted coding and prepared source.
- Predict: Ask: What changes when an input reaches the edge of the rule?
- Run Code: Read the actual Console or operate the prepared DOM controls.
- Step Through: For pure code, inspect the first recorded snapshot, then select Next Step. For DOM examples, inspect the live tree and event path instead.
- Load Example: Choose example 2 in Prepared example, click Load Example and confirm the replacement, and read why its result differs.
- Run Code: Compare actual behavior with its expected result.
- Reset Code: Confirm replacing the demo source with its prepared program.
- Explain: Ask the learner to explain one operation and propose a new boundary input.
Expected observation: true
Teaching explanation: At a data boundary, validate required fields and their types before using them. A truthy object alone is not enough. This check intentionally requires an integer ID, a nonblank title and a boolean completion flag. AI suggestions need a contract and tests. Inspect generated code, predict its behavior and verify it. Do not upload private data or credentials when requesting help.
Closing: What would you change next, and what result would prove that it works?
Reusable classroom worksheet
- Objective: what observable skill are you practicing?
- Prediction: write the expected result before running.
- Observation: copy the actual result or error.
- Hypothesis: which operation explains the difference?
- Repair: identify exactly what changed.
- Evidence: normal case, boundary case and observed output.
- Explanation: describe why the change works and a remaining limitation.
- Transfer: apply it in a new example without the reference answer.
Assessment rubric
Check functional evidence, causal explanation, boundary awareness and independent transfer separately. A pass or long explanation alone is not proof of mastery. Have learners review the same case using an alternative implementation.