WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.
State changes with vary
A binding connects a useful name to a value. A readable name explains what that value represents in the mod. A stable value and a changing count should not look identical in the code: making their different roles visible reduces accidental edits.
- 1→
State changes with vary — Discover and trace
Make a prediction before touching the example.
Open practice - 2→
State changes with vary — Build the smallest useful slice
Change one useful behavior while keeping the contract small.
Open practice - 3→
State changes with vary — Change one requirement
Translate one new mod requirement into a deliberate change.
Open practice - 4→
State changes with vary — Boundary detective
Find a case the simplest success path does not cover.
Open practice - 5→
State changes with vary — Flash-check repair
Use a plausible mistake to show that you understand the mechanism.
Open practice - 6→
State changes with vary — Connect the previous skills
Connect this idea with a previously learned responsibility.
Open practice - 7→
State changes with vary — Review and demonstrate
Collect a useful learning record without pretending the code was executed.
Open practice - 8→
Module project — Workshop stock counter
Turn the section work into one reviewable mod feature.
Open practice