你最难以解决的bug的最佳做法是什么？ [英] What are your best practices for bugs that are hard to solve?
问题描述
我有时会发现自己试图修复一个顽固的错误，只有在一段时间之后，才明白出现一些非常明显的错误。
I sometimes find myself trying to fix a stubborn bug and only after a while figuring out that something quite obvious was wrong.
当我认为问题与某些事情有关，我对其他可能会出错的事情感到盲目。
This happens to me when I think the problem is related to something and I kind of get 'blind' for other things that can be wrong.
大多数时候，有一天睡觉有帮助第二天早上，我马上看到这个问题。
Most of the time it helps to have a night of sleep and the next morning I see the problem immediately.
过去发生在我身上的事情：
Things that happened to me in the past:
- 编辑没有任何效果的真实源文件的副本。
- 不关注真正的问题，而是在真正的问题已经解决的同时想出一些东西
- 不要像以前一直在使用解释语言一样编译/构建。
调试过程中你的盲目经历是什么？
What are your 'blinding' experiences during debugging?
推荐答案
有一点很有帮助，和不要迷恋
One thing that helps a lot is to find a good balance between focussing and not obsessing.
- 确保您可以在不受干扰的情况下处理该错误
- 但也知道什么时候休息，如果你不能再集中了
是的，有一个点，一个晚上的睡眠是最好的你可以做。
And yes, there is a point where a good night of sleep is the best you can do.
最后，与同事讨论问题，经常是第二双眼睛和观点工作的奇迹。令人惊讶的是，有时只是解释问题已经有所帮助，即使听众没有说什么。这被称为橡胶鸭调试。
Finally, discuss the problem with a colleague, often a second pair of eyes and point of view work wonders. Surprisingly, sometimes just explaining the problem already helps, even if the listener does not say anything. This is called Rubber duck debugging.
这篇关于你最难以解决的bug的最佳做法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
