debugging

From README

Debugging Read and analyze first, change code last. Most debugging failures come from jumping to fixes before understanding the problem. --- Reproduce First Confirm the failure before touching anything. Run the failing test, hit the failing endpoint, trigger the broken flow. If you can't reproduce it, you don't understand it yet. --- Read Everything Before theorizing, read: The full error — the entire stack trace, not just the first line. The root cause is often buried deeper. The logs — application logs, server output, build output. They often tell you exactly what went wrong. The browser console — for frontend: console errors, network failures, failed requests, and CORS issues tell you more than the UI does. Check the Network tab for status codes and response bodies. The code — trace the actual execution path from entry point to failure. Don't guess what the code does — read it.