Check out my free resources and deep-dive courses. A little something I made When I’m not writing about code, I design geeky mugs. If you’d like one for your desk, or know someone who would, take a look at my…
annoying bugs I deal with. Nothing in the logs. No stack trace. Just a slow climb until the process gets killed.
and validate the evidence before recommending a root cause? Most AI debugging demos start with a clean error message and end...exception may be a symptom of the failure—not its root cause. The first agent doesn't diagnose. It extracts.
I recently came across an interesting memory leak scenario which caught me off-guard, let’s see...straight-forward way to start an investigation into a Node memory leak when you can run the project locally (debugging in production is a different matter!)…
Datadog alerts across the stack and returns a root cause, supporting evidence, and next steps. Read-only...metrics, logs, and traces you already collect into root cause evidence. Compare behavior across the incident
A flaky test gives you an unusually valuable experiment: the same test failed and then passed inside one recorded run. Instead of rerunning it until the failure disappears, compare the attempts. The Cypress Cloud CLI exposes Test Replay commands, network…
In a critical batch process, an unexpected exception caused pipeline termination: the number of account records matching a specific balance threshold retrieved at the beginning of a transaction did not match the count retrieved during a subsequent step within the…
The flaky test was the kind that everyone on the team had learned to rerun. It failed maybe one run in twenty on CI. Locally it never failed at all. The usual ritual was: hit retry, move on. When the agent…
project that i have worked on is breaking into the debugger programmatically. Eventually, most codebases end...standard way to handle this. Thanks to P2546R5 (Debugging Support) and a later refinement in P2810R4 (is_debugger_present is replaceable), we have the new header:...This is…
tighter-than-expected timing budget, or a slow memory leak that only manifests after prolonged uptime....faults often appear as patterns rather than clear stack traces. Identifying the root cause usually involves systematically ruling out the...real-time constraints, resource management, and debugging…
Debugging techniques, stack traces, reproducing bugs, memory leaks, race conditions, profilers and war stories from production.
An article joins this feed when it matches these terms. Each one is also a search of its own.