Explainers
Short pieces where you learn the idea by moving something.
Coding agents
How to tell whether an agent is doing the right job, from running a team of them on S4mple.
-
What one trial hides
An agent that passes a case once may fail it the next time. See how fast "passes every time" falls away.
move the pass rateopen -
Hook or eval?
Six real rules. Which can a script enforce, and which need judgment?
sort six rulesopen -
Act or ask
Eight situations from my agents' ownership rules. Should the agent go ahead, or stop?
sort eight situationsopen
Simulators
Three full simulators I built for a talk on why systems wait. Each one isolates a single mechanism, and you drive it by hand.
Scheduler
Tasks contending for machines and locks. Concurrency against parallelism, the cost of switching, and how a deadlock forms.
place tasks, add machinescoming soonWhere should the bytes live?
Twenty-four bytes, one hue each. Move them between tiers and watch what each query pays to read them.
drag bytes, run queriescoming soonThe departure process
What limits, queues and retries do to a flow of requests: waiting, overload and the cost of refusing.
set limits, replay the hourcoming soon
The squares, colours and controls are the ones S4mple's simulators use. S4mple is the learning app I'm building, where pieces like these can be saved as notes.