debugging

Collect all relevant context about the issue: Error details : Environment : Create a minimal, reproducible example: Use binary search debugging to narrow down the issue: Print/Log debugging : Divide and conquer : Common bug patterns and solutions: Questions to ask : Apply the fix with proper verification: Fix checklist : Ensure the fix works and prevent regression: Error : Analysis : Symptom : Test passes locally, fails in CI intermittently Analysis : Tool : Use memory profiler - Encountering runtime errors or exceptions - Code produces unexpected output or behavior - Performance degradation or memory issues - Intermittent or hard-to-reproduce bugs - Understanding unfamiliar error messages - Post-incident analysis and prevention - Full error message and stack trace - Error type (syntax, runtime, logic, etc.) - When did it start occurring? - Is it reproducible? - Language and version - Framework and dependencies - OS and runtime environment - Recent changes to code or config - What changed recently? - Does it fail with specific inputs? - Is it environment-specific? - Are there any patterns in failures? - Reproduce first : Never fix what you can't reproduce - One change at a time : Isolate variables when debugging - Read the error : Error messages usually point to the issue - Check assumptions : Verify what you think is true - Use version control : Easy to revert and compare...