Something I’d add to the “Take breaks” section is to get some sleep. So many times we end up figuring out a solution to a bug while sleeping. It helps a lot!
The document part is so often overlooked. I mostly use a simple excel spreadsheet, where I have a column for the time, and additional column for each service/app. That way I can paint a clear picture of what causing the bug.
Before that, I remember going to the logs again and again to understand the picture - especially in more complex bugs.
Great write up!
Something I’d add to the “Take breaks” section is to get some sleep. So many times we end up figuring out a solution to a bug while sleeping. It helps a lot!
Definitely. Sleeping is a great tool to reset the mind and start fresh. Thanks for adding this, Chemil!
I like the emphasis you put on documentation, Basma.
If we reach the point where we need debugging, it's often because there's no documentation around this kind of issue.
It would be a waste to fix the issue without leaving the knowledge base better for the next time
Definitely. I feel deep gratitude for people who document their fixing process. It saves great deal of time.
The document part is so often overlooked. I mostly use a simple excel spreadsheet, where I have a column for the time, and additional column for each service/app. That way I can paint a clear picture of what causing the bug.
Before that, I remember going to the logs again and again to understand the picture - especially in more complex bugs.
Using excel sheet is very interesting. Looking at logs at first may mean nothing, but going back to logs over and over will help you connect the dots.
Great tips, Anton! Thanks for sharing :)