When debugging issues in UAT, what information do you end up recreating by hand?
Logs, state, timing, data, versions, or something else?
Ask HN: What's the one missing detail that usually makes a bugs hard to debug?
1–3 of 3 posts
Re: Ask HN: What's the one missing detail that usually makes a bugs hard to debug?
#2My biggest roadblocks come from my own certainty that I wrote correct code. That leads me to look in the wrong places for the bug. I have repeatedly looked right at bugs and not seen them because I felt sure that code works as expected.
Re: Ask HN: What's the one missing detail that usually makes a bugs hard to debug?
#3My biggest roadblocks come from my own certainty that I wrote correct code. That leads me to look in the wrong places for the bug. I have repeatedly looked right at bugs and not seen them because I felt sure that code works as expected.
This resonates. A lot of debugging time isn’t spent finding where the bug is, but unlearning the assumption that “this part is obviously correct.”