Break
Don’t start Break with jargon. Start with a Break dry-run. That is the whole point.
Break order — meaning → one Break step Dev can write from memory → one limit. Dumping ten features helps nobody.
Break exists so Dev can keep a Break dry-run correct in a campus project.
Break shows up in a campus project. Name a Break dry-run, not “a real-world scenario”.
Don’t do this with Break — skipping the failure case for Break. Interviewers spot it in ten seconds.
After Break, Dev should still remember skipping the failure case for Break.
One breath for Break, then a Break dry-run, then skipping the failure case for Break. Sit down.
Say Break in one breath, then one Break step Dev can write from memory, then skipping the failure case for Break.