Does systematic workflow to undertake polyglot Codebase ownership exist?
Is it possible to come up with a systematic workflow to accelerate the process of inheriting ownership of a legacy polyglot codebase? The core use case is to understand a distributed system with close to no documentation, no class diagrams, very few comments and a very reluctant couple of engineers who might know dependencies but not willing or "too busy" to build the dev docs. Tool...