Debugging. Memory leak hunting, figuring out latency issues
For things where I'm not familiar with the code base, it can take days or weeks to become familiar with structure and flows.
If I can get an agent to help visualize and analyze the architecture and zero in on a subset of code, that can be a huge win.
For instance, we had some archaic "cache" that just dumped things into a static/module-level map. I tried a few different things to try to find it over the course of a few days and eventually gave Claude a Python REPL into a running process with pyrasite after some memory leaked and it traced through heap allocations and references to find the referent. It would have taken me probably 2-4+ weeks of just learning about Python heap to figure that out of my own.
For things where I'm not familiar with the code base, it can take days or weeks to become familiar with structure and flows.
If I can get an agent to help visualize and analyze the architecture and zero in on a subset of code, that can be a huge win.
For instance, we had some archaic "cache" that just dumped things into a static/module-level map. I tried a few different things to try to find it over the course of a few days and eventually gave Claude a Python REPL into a running process with pyrasite after some memory leaked and it traced through heap allocations and references to find the referent. It would have taken me probably 2-4+ weeks of just learning about Python heap to figure that out of my own.