debugging-patterns

Systematic debugging follows a structured workflow: capture the problem details, isolate the affected code or environment, hypothesize the root cause, and verify your fix. This approach works across ABP Framework and React applications, using IDE debuggers, logging, and profiling tools to trace execution and pinpoint issues efficiently.

For production issues, enable detailed logging, attach a remote debugger to running instances (Docker containers, cloud environments), and analyze stack traces and error messages. Post-mortem analysis of crash dumps combined with systematic tracing of the execution path reveals root causes of intermittent failures.

N+1 queries and async deadlocks require profiling and stack trace analysis using IDE debugger watch expressions and logging. The debugging patterns Skill provides concrete C# and EF Core examples for diagnosing query performance and async execution flow problems.

Yes. React state debugging uses IDE debuggers to set breakpoints in component lifecycle and event handlers, combined with logging state changes. The Skill covers TypeScript/React debugging patterns and techniques for isolating state mutation problems.

IDE debuggers (breakpoints, watch expressions), logging frameworks, and profiling tools form the core debugging toolkit. The Skill teaches how to apply each tool strategically across different bug types—from test failures to production crashes—to narrow down root causes.

Remote debugging requires knowledge of attaching debuggers to running processes in Docker containers and cloud instances, plus interpreting remote logs and error reports. The Skill provides patterns for these environments without extensive prerequisite knowledge of container internals.