Design walkthroughs, drawn rather than decked

Field notes

The page frames a walkthrough as a single evolving artifact rather than a diagram that must be rebuilt into a separate presentation. Its worked example follows a file through a queue, bounded retries, and a dead letter queue, giving the concept a concrete systems-design context. The described access model is per walkthrough: an invitation reaches one page, and users authenticate with Google instead of creating or sharing a password.