If you're ever stuck on a bug for more than ~15 minutes, type out a precise explanation of the problem as if you're sending it to a team member for help.

Include everything you've thought of and/or tried as well as any additional context you think might be related.

You'll find the issue before you're done typing it all up. In the rare cases you don't find it, make one editing pass and send the email.

Alternatively, describe the problem out loud to nearby pets or plants. It works. Guaranteed.

@garrettdimon @dekkzz76 I can agree to that. Another thing that I have started, is to keep a journal of what I am. Trying and the lessons I am learning g, this combines the writing part plus it helps when getting back to the bug later where you then do not have to recreate the commands etc you used in the previous session. If one is into #emacs, then #orgmode is very handy for this.