I never bothered to write down details of bugs... I rarely learn a lesson from any one specific bug - Lessons are learned by being exposed to a wide range of different bugs over many years. Eventually it becomes gut instincts.<p>For example today I was debugging an issue with Kubernetes (it was a really cryptic error about client-server not being able to negotiate a protocol or similar). I had never used Kubernetes before and I couldn&#x27;t find anything on Stack Overflow.<p>The first thing I did was check the client and server versions (to see if they matched) - They did so that wasn&#x27;t the issue. So then I had a strong &#x27;gut feeling&#x27; that it was related to the client configs.<p>In this case, my second hypothesis turned out to be correct. 5 years ago I would probably tested my way through 20 different hypotheses before finding the problem.<p>To summarize my debugging strategy, it&#x27;s simple; just pick all the low-hanging fruits first. The hard part is knowing what a low-hanging fruit looks like.