3 ms·
I agree - debugging is an integral part of programming. I don't mind debugging, and often bugs are good for you: - solving a bug teaches you something. You eit
by henrik_w 10y ago
I agree - debugging is an integral part of programming. I don't mind debugging, and often bugs are good for you:
- solving a bug teaches you something. You either learn something new about how to write good code, about the product or about the domain.
- debugging problems teaches you how to write code that is easy/easier to debug. You see what information you wish you have had, how to be able to track what is happening in the program etc.
- solving problems and mysteries (how can this even happen) is often fun in itself (like solving sudoku or crosswords or reading murder mysteries).
- when you resolve a bug, both you and your customer are happy. It's a bit of a paradox. If there wasn’t a bug in the first place, there wouldn’t be a need to fix it, so why should they be happy? However, my experience is that they are happy to receive a bug-fix, especially if it is solved quickly
More detailed argument here: https://henrikwarne.com/2012/10/21/4-reasons-why-bugs-are-good-for-you/ https://henrikwarne.com/2012/10/21/4-reasons-why-bugs-are-go...
- mrb 10y ago"debugging is an integral part of programming" Can't remember where I read this: programming is 20% writing bugs, and 80% fixing them.