Advertisement
So I'm interested in the group opinion about debugging techniques and how they relate to agile coding.
There's been a lot of push lately toward things like log4j for doing audit trails that are used for field diagnosis of code, and I've recently seen that creep back into the dev process, where coders basically litter their code with audit statements so if something goes wrong, they can read the log and actually debug that way. But of course, this leads to complete information overload when the logs are chugging out 30M a minute of goop when the code is being run in normal conditions.
Modern debuggers (at least for us java heads) have been getting lots and lots better lately (intellij rules!), and have been pushing me back towards the middle of the road on the extreme logging and towards the debuggers, just for speed of turaround on bug fixes, if nothing else.
I'm wondering how other folks feel about this, and if its something that has been crossing their minds.
There's been a lot of push lately toward things like log4j for doing audit trails that are used for field diagnosis of code, and I've recently seen that creep back into the dev process, where coders basically litter their code with audit statements so if something goes wrong, they can read the log and actually debug that way. But of course, this leads to complete information overload when the logs are chugging out 30M a minute of goop when the code is being run in normal conditions.
Modern debuggers (at least for us java heads) have been getting lots and lots better lately (intellij rules!), and have been pushing me back towards the middle of the road on the extreme logging and towards the debuggers, just for speed of turaround on bug fixes, if nothing else.
I'm wondering how other folks feel about this, and if its something that has been crossing their minds.
Advertisement
Advertisement
