Dependency Tracing Insights
Ironic..
I built a dependency tracer in C# which traces method invocation through a codebase. It produces a manifest of the relevant code as retrieval for RAG and also produces plant UML descriptors to create class and sequence diagrams
Running it against legacy code, I get a clean path from input source to database. Running it against my own tracer code, I get nothing useful.
Static analysis is not good at tracing runtime interactions like dependency injection and implementations behind interfaces. ie well architected code! After banging my head against it for a few hours, I realized it kind of works. If it finds nothing to rewrite, it found nothing worth rewriting…