If tacit knowledge is not something you can get by reading, then training and mentoring is much better (dare I say vital!) than documenting it all in a wiki, or

If tacit knowledge is not something you can get by reading, then training and mentoring is much better (dare I say vital!) than documenting it all in a wiki, or just making sure everything is done asynchronously in a well written pull request. This is a weird thing to argue. Productivity could be something like [system-knowledge] X [tacit-knowledge-of-programming] so just tacit knowledge wouldn't get a team maximum productivity. Altogether, it seems like what's tacit in programming or tacit in any complex domain is "how to integrate different complex and sometimes contradictory things". It's important but hardly important in a "you can discard everything else, this is the magic" sort of way.