Earlier quoted context omitted.
Is there another industry where a few employees with "domain knowledge" can sink a company? Asking because, while, yes, throwing money at the problem might be a solution, I think the obvious bigger issue is how does one allow themselves to get into this situation? Or rather, how does one avoid getting into this situation. Because it seems to me that the software industry of late has become so mired in esoteric layers…
> Or rather, how does one avoid getting into this situation. Documentation?
Significant documentation is also not something easily written in slack time. With any non-trivial project good documentation is a full time effort. It also needs to be updated as the project evolves lest it become out of date and incongruous with the behavior of the system.
There's dreams of in-line documentation but that's only going to cover individual methods and classes and not necessarily whole modules or major subsystems of a project. It's also not going to necessarily cover in-line documentation from other parts of a project in different languages e.g. comments in config files.
There's lots of technical ways to help documentation but there's no replacement for documentation being a high level project goal with resources allotted to it.