Debugging
Error detection and resolution
Debugging Tools & Techniques Framework
Build a debugging toolkit — selecting the right tool for each class of problem, implementing logging that provides diagnostic value without noise, and establishing the debugging workflow that finds bugs faster than trial-and-error code changes.
Error Message Interpretation Framework
Interpret an error message or stack trace — extracting the root cause from the stack, distinguishing the error origin from where it surfaced, and translating cryptic runtime errors into the specific code change that resolves them.
Frontend Debugging Framework
Debug frontend problems — from rendering bugs and state management issues to JavaScript errors and network failures, using browser DevTools systematically to locate the exact component, function, or network request causing the problem.
Network & API Debugging Framework
Debug network and API problems — diagnosing connection failures, timeouts, SSL errors, and intermittent failures with the specific tools and diagnostic sequence that locates whether the problem is DNS, routing, TLS, the remote server, or the application layer.
Database Debugging Framework
Debug database problems — diagnosing slow queries with EXPLAIN ANALYZE, identifying blocking locks, tracing data integrity violations to their source, and investigating connection pool exhaustion without taking the database offline.
Async & Concurrency Debugging Framework
Debug async and concurrency problems — identifying race conditions, deadlocks, and unhandled promise rejections through the specific diagnostic techniques that make timing-dependent bugs reproducible and fixable.
Performance Debugging Framework
Debug a performance problem — using profiling to locate the bottleneck before optimizing, distinguishing CPU-bound from I/O-bound problems, and making the smallest change that produces the largest measurable improvement.
Memory Leak Debugging Framework
Debug a memory leak — using heap snapshots and allocation profiling to identify what is accumulating, tracing back to the code that creates the accumulation without releasing it, and fixing the leak at the source rather than masking it with restarts.
Production Incident Debugging Framework
Debug a production incident — with a structured triage process that separates mitigation from root cause analysis, uses logs and traces to locate the failure point, and produces a post-mortem that prevents recurrence.
Systematic Debugging Framework
Debug a software problem systematically — formulating a falsifiable hypothesis, designing the minimal experiment that tests it, and following a diagnosis process that finds the root cause rather than the first plausible explanation.