57
The Tacit Dimension: Why Your Best Engineers Can't Tell You What They Know
(cekrem.github.io)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 May 2026
57 points (93.8% liked)
Programming
28304 readers
421 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
No. When we communicate, we're not really communicating our knowledge or understanding, we're communicating a crystallization of it in a form the listener might be able to learn from. The communication and the understanding are fundamentally different things. Like a map to the terrain. If they were the same, would we not be able to understand something purely by hearing it?
What's communicated is an imperfect projection of what is understood - fine. It doesn't matter they're not the same.
Take whatever the senior engineer concluded after that hour and document that for the next time something like this happens.