[hoistbypetard]

I'm not sure what lesson to draw either, but I kind of suspect that the situations where this tool adds the most value (e.g. a developer needs to jump into a code base without anyone around to help orient exploration) are also the situations where there's least likely to be funding. And in that particular example, if the developer is new to the org, it is a situation where they're unlikely to know how to/feel comfortable asking how to gain funding.

[johannes1234321]

Such a tool is not only useful for a junior. It is also useful for (incomplete list I assume)

* The consultant coming to a project for a short period of time

* The software architect, observing the code layout periodically (for example to identify where lower layers of the software depend on higher layers)

[TeMPOraL]

Yes. Also, unless you define seniority on a per-company level, derived from actual time spent in the company, then you'll have plenty of senior developers landing in the middle of a legacy codebase that's new to them.

(And then, there are projects you look at very briefly. Just a few days ago, I used Sourcetrail to explore a certain research CLI application. I mostly needed to know how it does a few particular things, and Sourcetrail was useful for finding my way around the exceedingly complex class graph quickly.)

There's no good tool out there for reading source code. Sourcetrail is a step forward that's useful for anyone.