In other words the unspoken knowledge can be learned from two sides, not one. It's understandable that the author focuses on their side, but I don't think he does so with the intention to discourage "the effort to make [the knownledge] explicit".
> My take on this is that it is so difficult that we shouldn’t even bother; assuming that you are reading this because you want to get good in your career, you should give up on turning tacit knowledge into explicit knowledge and just go after tacit knowledge itself.
> Why do we know this? > [What many researchers found out] was that it is extremely difficult to encode all the possible branches and gotchas and nuances from a human expert into an expert system.
To me that sounds like a direct analog to "nobody will ever understanding everything about the source code without reading it, so we shouldn't bother with documentation".
Obviously we can't / shouldn't document everything, but creating documentation as you learn an undocumented legacy code base can be of great value (as can asking other developers to explicate their implicit knowledge).
Over and over the Author ignores the unexplicated but explicable and assumes that implicit knowledge is inexplicable.
Clearly unspeakable knowledge is a subset of unspoken knowledge, but there is definitely unspoken knowledge that is speakable if we take the effort to make it explicit.
"things awkward people need spelled out" is a great example of tacit knowledge that is often speakable (but we don't bother because the tacit assumption is that the tacit knowledge is shared by all.)
By conflating the unspoken with the unspeakable, the author fails to realize that a great deal of our tacit knowledge can be made explicit or at least partially explicit (and the value that can be captured by finding new ways to explicate the formerly unspeakable.)