Let’s do it!


What’s the life of a developer?

Answer: coding for about 1/3 of the time and debugging for the rest of the time…

This is a quite frustrating job. Whatever you are doing, even if you are very careful during the development, you are going to have a multitude of bugs. That is why the role of tester exists! Because we are not able to develop something with no bug… And even with a test team, we are still selling buggy software (best example: Windows :D).

After five years of fixing bugs (which are not always mine of course ;)), I thought it would be a good idea to create a blog explaining the solution for these problems.

I hope this will help some of you. If yes, don’t hesitate to leave a comment! 🙂


  1. #1 by Manjit on 18 Nov 2009 - 12:37

    Totally agree Steph – writing code is the easy part, figuring out and fixing why it doesn’t do what it’s supposed to is what separates the good programmers from the bad.

  2. #2 by Shaha Alam on 02 Dec 2009 - 19:15

    Some would argue that debugging is part and parcel of the coding process n’est-pas?

    you wouldn’t expect to write your code once, compile just once, and then deliver would you? by the same token, you’re likely going to write, compile, test, write, compile, test, fix, compile, test, fix, compile, test, write…etc.

    it’s more like 1/3 coding (which includes debugging) and 2/3 complaining/blaming the previous developer. 🙂

  3. #3 by smoreau on 03 Dec 2009 - 15:52

    Shaha Alam :

    you wouldn’t expect to write your code once, compile just once, and then deliver would you?

    Well, this is one of my dream! How much time could we save if we were able to write the code once and ONLY once? 😉

    Shaha Alam :

    it’s more like 1/3 coding (which includes debugging) and 2/3 complaining/blaming the previous developer.

    This is too true! lol It is so easy to complain about the previous developer. But sometimes we are right to blame him, didn’t we? 😉

(will not be published)