@jayeless yes, I think every time I stop at the end to reflect what went wrong in this particular debug session it is “changed more than just a one thing" and “was tired”. My own optimal debug flow is nowadays: * Have a break first * Think of the ways this issue could be systematically explored * Try things one at a time * Have another break * iterate until fixed * Reflect: Think of the ways this issue could have been systematically explored. Think of the ways we would have had this issue at all * Take notes for future

I’ve been meaning to write about debugging, but this tweet thread came up on my timeline and this is excellent: Being a software engineer requires some detective work when things go wrong🕵🏾‍♀️HINT: the computer is probably doing exactly what you’re telling it to do but here are some mo... blog.timokoola.com

2021-05-13 2:50 pm

|

Embed

jayeless

@tkoola That is a good thread! Not that I'm a software engineer, but I try to do many of those things working on software projects and it's good advice to live by. Especially "only change one thing at a time"… how many times have I made an incorrect assumption about what was breaking because I committed a number of changes at once 😒

2021-05-14 12:56 am

|

Embed

In reply to

tkoola

@jayeless yes, I think every time I stop at the end to reflect what went wrong in this particular debug session it is “changed more than just a one thing" and “was tired”. My own optimal debug flow is nowadays:

Have a break first
Think of the ways this issue could be systematically explored
Try things one at a time
Have another break
iterate until fixed
Reflect: Think of the ways this issue could have been systematically explored. Think of the ways we would have had this issue at all
Take notes for future

2021-05-14 9:27 am

|

Embed

Micro.blog

Micro.blog