Filters
Don’t start Filters with jargon. Start with a Filters dry-run. That is the whole point.
Filters order — meaning → one Filters step Dev can write from memory → one limit. Dumping ten features helps nobody.
Skip Filters and skipping the failure case for Filters shows up in a first job task.
Dev ships Filters in a first job task. That is the use case worth saying.
Don’t do this with Filters — skipping the failure case for Filters. Interviewers spot it in ten seconds.
After Filters, Dev should still remember skipping the failure case for Filters.
Close Filters with — “If I skip it, a Filters dry-run goes wrong like this: skipping the failure case for Filters.”
Board: a Filters dry-run. Dry-run Filters. Name the trap: skipping the failure case for Filters.