GuideTechnology
18 min read
A method for finding bugs instead of guessing: read compiler errors and stack traces properly, form and test hypotheses, use breakpoints and stepping in a debugger, log usefully at the right level, and reach for thread dumps and heap dumps when the problem is a hang or a leak.
GuideTechnology
10 min read
AI-written code often passes AI-written tests, because both come from the same assumptions. This article shows how to write tests that check what the code should do, how to use AI as a second reviewer without relying on it, what to look for in AI-generated diffs, and how to refactor safely.
GuideTechnology
9 min read
Pasting an error into an assistant can solve a bug in a minute, or produce a patch that hides it. This article gives a safe debugging workflow: reproduce, share safely, ask for hypotheses, test them, review the fix, add a regression test, with a worked example and a list of dangerous 'fixes'.
GuideTechnology
7 min read
Random changes and hopeful refreshes waste hours. This is a step-by-step debugging process that works in any language: reproduce, narrow down, form a hypothesis, test it, then fix the cause.
