3 ms·
"never think about the bug again" That has never been part of the process. That may be what some people do, but it's not part of the process. Good programmer
by wccrawford 16y ago
"never think about the bug again"
That has never been part of the process. That may be what some people do, but it's not part of the process.
Good programmers figure out how the bug happened -while- they are fixing it. There's no need to spend time afterwards. (Okay, there are a -few- cases that require research, but I've never met one of those that didn't require me to track it down anyhow.)
- darkxanthos 16y agoThe reason he gives for spending time afterwards is at the end of the month to allow you to review a pattern across all of the bugs you worked on recently. That's difficult to do with just your memory. Just figuring out and understanding a bug is not enough. His point is to figure out and understand how bugs are manifesting themselves in your system... Slipping through all of your safeguards... showing your lack of control of your code.