What keeps coming up is that the hardest part isn’t generating docs or summaries. It’s preserving understanding as repositories grow in size, language mix, and history.
I’m curious how teams here handle this in practice.
Do you rely on conventions, internal tooling, documentation, or mostly social knowledge? What tends to break first as a codebase gets older?
Anything less is a very poor substitute at best.
IOW you can rake in the bucks a lot of other ways, outperform your wildest expectations and be perfectly satisfied financially, but you're really quite poor by comparison to how rich you would be if you did it right from the beginning.