systematic-debugging

Follow the four phases: investigate the root cause by reading errors and reproducing consistently, analyze patterns against working examples, form and test a single hypothesis, then implement one fix verified by a failing test. Never stack multiple fixes at once.

Trace backward through the call chain from the immediate cause to the original trigger, asking what called each level and what value was passed. Add stack trace instrumentation with console.error before the failing operation if manual tracing stalls.

No. Systematic debugging is faster than guess-and-check thrashing even under time pressure. Quick symptom fixes set a bad pattern, mask the real issue, and typically cause rework and new bugs.

Replace arbitrary setTimeout or sleep delays with condition-based waiting that polls for the actual condition you care about, such as an event appearing or state changing. Only use fixed delays when testing documented timing behavior.

Stop attempting more fixes and question the architecture. Repeated failures where each fix reveals new problems elsewhere indicate a fundamentally wrong pattern, so discuss refactoring with your team before trying fix number four.

Single-point validation can be bypassed by other code paths, mocks, or refactoring. Apply defense-in-depth by validating at every layer data passes through: entry points, business logic, environment guards, and debug instrumentation.