Émile Perron
At work, I kept hearing other programmers and developers complaining about things not working, only to find out a few minutes into helping them that they had made a very simple mistake. Oftentimes, they had already spent a lot of time trying to figure out what was wrong, but they were looking everywhere except in their own code (or they did look at it, but for a very short amount of time).
After a while, I started picking up the same type of thing in my regular conversations. People were facing issues, and looking at everyone but themselves; playing the "blame game", as I like to call it.
That's when it clicked in my mind!
From this point on, I started writing down my thoughts about the mindset I use when debugging code, and I tried to word it in such a way that it could be applied to the problems that people face in their everyday life. And that's how When in Doubt came to life!
After a while, I started picking up the same type of thing in my regular conversations. People were facing issues, and looking at everyone but themselves; playing the "blame game", as I like to call it.
That's when it clicked in my mind!
From this point on, I started writing down my thoughts about the mindset I use when debugging code, and I tried to word it in such a way that it could be applied to the problems that people face in their everyday life. And that's how When in Doubt came to life!
More Answered Questions
About Goodreads Q&A
Ask and answer questions about books!
You can pose questions to the Goodreads community with Reader Q&A, or ask your favorite author a question with Ask the Author.
See Featured Authors Answering Questions
Learn more