But the author doesn't say "don't only try to turn implicit knowledge into explicit knowledge", he says "you shouldn't even bother". To me that sounds like a d

But the author doesn't say "don't only try to turn implicit knowledge into explicit knowledge", he says "you shouldn't even bother". 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.