Show feedback even when complete is checked. Could be worth reading, a note about an improvement.

Make a clearer input validation example.

Split flag from subroutines. Move flag before subs.

Content review: up to reusing code.

Grading interface – list the rubric names to give grader a quick overview.

When complete is checked, show a Good! or whatevs. Otherwise, just show the list of rubrics.

Exercise list w/ filter, add Edit link to exercise listings.

Grading interface:

  • Separate list of just the rubric titles – helps get an overview of the requirements.
  • Overall eval – make a separate clickable item. Maybe from list of items in persona.
  • Access lesson containing exercise (see context).
  • Get rid of 40/80% thing. Just complete/not summary items.
  • Notes at the bottom of exercise. Use panel for something else.


if not isnumeric(userInput) Then
End if
c = userInput

… to…

if not isnumeric(userInput) Then
  c = userInput
End if

Otherwise, Ss run "c = userInput" without error checking, when the End is removed.

Start with mechanics of assignment statements. Assignment statement is an action. Using a var in an expression is an action.

Add example in subs, showing that it is the order of the params that matters, not name.

computeThing cats, dogs

Sub computeThing dogs, cats

Subs – lots more. They don't get it.

Start with a section on the mechanics of subs, before talking about designing code with them.

More specific commenting rules for subs – use param doc standards.

Sensible dates is not sensible.

Code organization

nested ifs.

More demos by pseudents showing how to use patterns in problem solving.

Review patterns. The right set? Consistent, and complete(ish).

Finish documenting patterns.

Finish documenting Big Ideas.

Challenge exercises, ideas for people who want to do more.

Update outline in blueprint.

Exploration pages.


draw three cars – is it used?

draw office building – clearn it up

Remove discussion of functions – use subs only.

Improve learning of some basics, e.g., logical expressions in if statements.

Mental model of VBA. Two boxes, program and memory. Connections to stuff outside. Excel, other things.

Programs don't care what you are trying to achieve.

Don't rely on just copy-and-paste patterns. Need to understand how each one works, because you usually have to modify them.

Start by developing a strong notional machine. Use it to statements, e.g., if. Not much of a connection of goals at this point.