3 ms·
But what if there are hundreds of developers working on a project, and I need to discover if the bug is caused in my own module or somewhere else? It seems to m
by greyman 18y ago
But what if there are hundreds of developers working on a project, and I need to discover if the bug is caused in my own module or somewhere else? It seems to me that the article was written from the perspective of pet-project programmer who mostly deals with his own code only.
- Deestan 18y agoI agree with that. When working on crappy code that is under the control of other teams (or worse, nobody), I find myself having to use the debugger quite often. On crappy code that's under full ownership of me or my team, we can (and do) clean up the code and leave the debugger on the shelf.
- jcromartie 18y agoCode that you didn't write is basically just a black box. This is even more true if it is undocumented or written in a way that makes it hard to glean information from the code. There is no way I could feasibly sit down and understand the entire flow of their code (especially when it is very poorly principled to begin with). I can manage without a debugger when I handle the code, or when the abstractions in use provide great error handling... but when it's just a giant pile of somebody else's barely-structured cowboy code? Debugger, please! At the moment I'm working on a massive system composed of about 4 years worth of code (written by someone who will readily confess that they are not a programmer) with no step-through debugger. There's a lot of printf going on and at times it is an extremely painful process.