3 ms·
I find myself writing debugging tools all the time. For example, our logs are overwhelming because our developers use them for debugging and then never remove t
by thewebcount 7y ago
I find myself writing debugging tools all the time. For example, our logs are overwhelming because our developers use them for debugging and then never remove their logging statements. So finding anything in them is next to impossible, and it's often interleaved with a bunch of other junk that's meaningless to you. And fixing the logging system we use would to make this work better would also be a huge task.
So a little while ago we needed to log some info to figure out where 2 parallel sets of calculations were going wrong. So I wrote some logging that output the info to a file instead of the main log, and then wrote a simple parser to read them in and display them side-by-side in a nice hierarchical tree structure. It made something that normally takes us a week to work out only take a few hours. It's something we'll never ship to customers, but helps us enormously.
I'm finding myself writing more and more stuff like that these days.
- stjohnswarts 7y agoYou might also try to get your QA process to require removal of debug print messages or at the very least an "off" flag as an environmental variable or config file element