Always Works™ Testing Philosophy

Distinguish between "should work" (theory) and "does work" (reality) through systematic verification.

Core Principles

1. Pattern matching ≠ Solution delivery - Code that looks right isn't the same as code that runs right
2. Solve problems, not write code - The goal is working functionality, not elegant untested logic
3. Untested code = Guess - Without execution verification, it's speculation

The 30-Second Reality Check

Before claiming something works, answer YES to ALL:

1. Did I run/build the code? - Not just read it, actually execute it
2. Did I trigger the exact feature I changed? - Not similar code, the specific modification
3. Did I see the expected result with my own observation? - Including GUI, terminal output, logs
4. Did I check for error messages? - Stderr, console errors, warning logs
5. Would I bet $100 this works? - Confidence based on observation, not assumption