Ever had to work closely with someone else to debug a problem? Maybe there’s a nasty bug that Alice can’t reproduce, but Bob seems to hit it every time. In large software projects, Alice and Bob might not even work for the same company: one company doing integration reports problems with a component that another company built… but problems that are only visible in the integrated system.
In situations like that, it’s often a good approach for Alice to use trace analysis in Sourcery CodeBench to understand the problem. If Alice could directly access Bob’s system over the network, Sourcery CodeBench would automate collection of the trace data, and then she could use Sourcery Analyzer‘s powerful trace analysis features to debug the problem. However, Bob is behind a different firewall, and he doesn’t know how to collect the trace data. What to do?
In the old days, Bob would need to knuckle down and learn how manually collect the data Alice needs, and probably do it repeatedly (and without typos) as Alice narrows in on the problem. Bob would be annoyed at the time commitment, Alice would get frustrated at the errors and slow turnaround time, and they’d be unhappy with each other.
No longer. Now Alice can use Sourcery CodeBench to generate a standalone script that takes care of all the trace data collection. She emails it to Bob, Bob runs it and emails the results back, and everybody’s happy.
Oh, and the bug gets fixed faster. What’s not to like?
Try it out now as part of a free evaluation of Sourcery CodeBench!