So many amazing thoughts in this article that apply to the world of software engineering. If tacit knowledge is as important as the author makes out, then hiring "young guns" is always going to have a cost over hiring people that have done it before. As an older developer, that's interesting to me. A contrary point, however, is that maybe all businesses are new domains of exploration, so you might as well pay the che…
It's also worth bearing in mind that tacit knowledge can lead you astray. And that tacit knowledge can be developed without having to be in the same room as someone. It's just that it's learned and communicated _differently_ than explicit knowledge. I think there's room to explore in the area of building exercises that try to build this tacit knowledge. Though some things are prohibitively expensive to learn outside…
How can tacit knowledge be learned without being in the same room with someone ?