WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.
Distinguish duration and idle TTL
Temporary data is not simply “data we hope will disappear.” Decide who owns it, why it exists, how large it may grow, how long it remains useful and what happens when cleanup cannot complete. These choices are part of the feature contract.
- 1→
Distinguish duration and idle TTL — Discover and trace
Make a prediction before touching the example.
Open practice - 2→
Distinguish duration and idle TTL — Build the smallest useful slice
Change one useful behavior while keeping the contract small.
Open practice - 3→
Distinguish duration and idle TTL — Change one requirement
Translate one new mod requirement into a deliberate change.
Open practice - 4→
Distinguish duration and idle TTL — Boundary detective
Find a case the simplest success path does not cover.
Open practice - 5→
Distinguish duration and idle TTL — Flash-check repair
Use a plausible mistake to show that you understand the mechanism.
Open practice - 6→
Distinguish duration and idle TTL — Connect the previous skills
Connect this idea with a previously learned responsibility.
Open practice - 7→
Distinguish duration and idle TTL — Review and demonstrate
Collect a useful learning record without pretending the code was executed.
Open practice
