
Make debugging suck less. Keep a logbook. đ
Scientists keep logbooks for their findings. Why donât computer scientists? A great place to start doing this is for debugging. Debugging sucks enough as is, make it easier on yourself. A logbook will⊠đș Enumerate where you are in the bug fix journey. Youâll forget this journey when you pick it up tomorrow, write it down. đł Keep you rooted to the ground. (Creating an âissue stackâ.) Related to above, it often feels like youâre completely lost in the aether when youâre 50 opened browser tabs deep into an issue thatâs not even the same issue anymore, its a sub issue of a sub issue. Youâre in a stack of issues. But, if you have each issue written down, as you solve one, you can pop it off the stack and solve the next issue one at a time. Keeping this stack in your head sucks, and its easy to conflate understandings from this current problem with the previous problem. ...