Live data from Hacker News

Tacit knowledge is more important than deliberate practice

commoncog.com

81–90 of 136 posts

Re: Tacit knowledge is more important than deliberate practice

#82
post #50
post #29

Wow. I have never really given this subject much thought. In thinking about it, it seems an important part of teaching tacit knowledge is to establish, or cause, conditions that encourage the learning — the experiencing — of the specific things you want to teach. Thinking back, I realize my own example of successfully teaching tacit knowledge was when I taught my son the first part of how to drive a car with a manual…

I do something similar with guitar. I can teach chords and notes, but I can't teach you how to hold the strings down properly in the first place. "Go play with this until you make the notes every time without a buzzing sound" basically.

I wish I could gift my callouses to beginners. It takes some time to build solid finger tips that can fret consistently at different angles, at the most discouraging part of the learning curve.

Re: Tacit knowledge is more important than deliberate practice

#83

I figured out something very similar in flight school. When I did my instrument rating, I realized my instructor, Sean, wasn’t perfect. No pilot is. But, I believed he could pass an instrument check ride. I could not. I decided that rather than figure out if everything he did was the best way or “worked for me”, I would just do my best Sean impression. I still had the opportunity to get even better by learning from o…

You never become exceptional this way. And if you run into situations you’ve never seen before, it’s harder to react competently. With coding, if you only ever use a style you copy, then everything looks like it could be solved in that way. This works and may help you up the corporate ladder. But it will never produce massively positive results

[deleted]

Re: Tacit knowledge is more important than deliberate practice

#84

> Tacit knowledge is knowledge that cannot be captured through words alone. This definition is slightly wrong. Tacit knowledge can't be described in words alone, but it can be captured through words alone. One of the reasons we built FWD:Everyone ( https://www.fwdeveryone.com ) was to capture the tacit knowledge contained within email conversations. When you can see the entire conversation, you learn how people inter…

> you learn how people interact with one another and you can learn to model your own communication based off of that. This strikes me a little like "By reading lots of good code, you can learn to model your own code based on that". It probably helps, but a lot is dependent on context. The blog post goes into this with the long quote about choosing tools and techniques for an appendectomy. How do you capture that sort…

> The blog post goes into this with the long quote about choosing tools and techniques for an appendectomy. How do you capture that sort of context in an email thread?

I mean in terms of our tool, the knowledge is either already in an email or it isn't. It's meant for retaining knowledge that's already being created anyway. You certainly could purposely capture knowledge in email for the purpose of being viewable and searchable in our tool (and some people do), but in that case there may be other better tools.

Re: Tacit knowledge is more important than deliberate practice

#86
In general, I agree with the notion that tacit knowledge is often more important than explicit knowledge - and that it may actually be the very essence of human expertise. However, it seems the author mixes some things up.

First of all, deliberate practice rests to a high degree on a) pre-existing knowledge on the structure of acquiring a skill and b) an established feedback standard that allows to evaluate your performance. These are obviously crucial aspects. If you don't know what characterizes expertise and if you don't know why you're not doing well - then it's difficult to make actual measurable progress. That said, it doesn't mean you can't become an expert at all in a field that does not have those elements currently available. It may just be that you need to put more effort into doing it, seek a mentor known for relevant skills or develop feedback mechanisms to evaluate your performance [1].

Thus, I don't think the distinction made between tacit knowledge and deliberate practice is really helpful. From my understanding, the concepts of "tacit knowledge" and of "deliberative practice" operate on two different levels. Tacit knowledge (or originally tacit knowing) refers to the implicit character of some knowledge. Its counterpart is explicit aka codified knowledge. Conflating deliberative practice with (the acquisition of) explicit knowledge seems counterproductive to me. It seems to me that the author wants to argue that deliberative practice only contributes to explicit knowledge.

I get that explicit knowledge may be needed to create learning environments (and gained before through codification of tacit knowledge) that respond well to the principles of deliberate practice. From my reading of Ericsson that does not mean, however, that deliberate practice only works to build up codified knowledge. Tacit knowledge is in itself a vague concept that is hard to grasp. I wouldn't be confident to assert that building up tacit knowledge happens without building up codified knowledge. Maybe someone knows more about that?

Another aspect of the article that concerns me represents the part about the acquisition of knowledge and expert systems. There seems to be another conflation of concepts. It is referred to Klein who (in reference to humans) warns about the overreliance on fixed procedures for decision-making. I agree with that but nevertheless I'm having a hard time with the argument in the article's context. For me this seems to be more of an argument about having a human making a decision than about the superiority of tacit knowledge over deliberative practice or even codified knowledge applied by a human. I get it, humans can build up tacit knowledge and therefore have an advantage over expert systems in previously unknown situations ... I just don't get the relevance for human acquisition of knowledge here which the article wants to be about.

A similar issue I have with the argument about the scope of deliberative practice and NDM as better alternative. Now I have to say I heard about the term NDM for the first time today (and I'm glad I got introduced, thanks!) but from what's written down in the article, it doesn't really seem to be in conflict with - or even that much qualitatively different compared to - deliberative practice: "you find a master, you work under them for a few years, and you learn the ropes through emulation, feedback, and osmosis". This seems to be possible under the concept of deliberate practice as well.

To get a better understanding, I've read another article from the same author [2] but I'm a bit confused. In the end, NDM just seems to offer more concrete procedures to acquire effective and adaptable mental models (in terms of deliberative practice) that help you to make better decisions. But that can't be the catch of NDM, is it?

[1] I'm currently reading Ericsson's book "Peak" and he mentions the Top Gun academy of the US Air Force as an example for the possibility to develop a "deliberative practice"-like environment.The program was designed to enhance figher pilots' performance by having those pilots surviving the initial air fights in Vietnam to become teachers to new pilots. Establishment of good practices took place through the constant exposure of the teachers to new recruits and constant training on usual fight situations.

[2] https://commoncog.com/blog/putting-mental-models-to-practice...

Re: Tacit knowledge is more important than deliberate practice

#87
post #13

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…

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 p…

I agree with you.

But, tell me if you think I'm wrong: I'm arguing that most software companies have a mentality like you describe: "you can discard everything else, this is the magic" about wikis, PRs (so they generally ignore mentoring and training, or at least don't want it on their employees schedules).

I think you are saying I'm saying that I think that mentoring and training allow you to throw the rest away. I'm not saying that.

Re: Tacit knowledge is more important than deliberate practice

#88

I figured out something very similar in flight school. When I did my instrument rating, I realized my instructor, Sean, wasn’t perfect. No pilot is. But, I believed he could pass an instrument check ride. I could not. I decided that rather than figure out if everything he did was the best way or “worked for me”, I would just do my best Sean impression. I still had the opportunity to get even better by learning from o…

You never become exceptional this way. And if you run into situations you’ve never seen before, it’s harder to react competently. With coding, if you only ever use a style you copy, then everything looks like it could be solved in that way. This works and may help you up the corporate ladder. But it will never produce massively positive results

Counterpoint: the better you get at copying, the faster you accelerate your ascent towards being exceptional. Copying is generally the beginning, not the end. By this anti-copying logic, practicing scales on an instrument shouldn't have any bearing on playing a complicated piece of music, only playing that piece, right? And yet, practicing scales until they're perfect and mastered pays dividends because the closer they get to second nature the more firmly they can serve as a foundation for second order skills.

Learning how to copy things is an art in and of itself. A lot of engineers (myself included) got into the craft by taking things apart and putting them back together again. It's true that you cannot become a good engineer /only/ by doing this, as at some point, you must learn how to create things from scratch that you've never taken apart and never put together before. It's true that teaches you a lot, but I think it's a little bit of a stretch to imply that it's the only thing that can teach you.

Re: Tacit knowledge is more important than deliberate practice

#89
The John Boyd example is super interesting. My understanding is that he essentially built a framework for thinking about dogfighting, the OODA loop. Very similar to how the author put kids on tiny bicycles. You can't tell someone what to think, but you can _design a system_ that makes it so that they think about the right thing at the right time.

Re: Tacit knowledge is more important than deliberate practice

#90
I believe deliberate practice can work in the same direction if the practitioner is aware of the fact that there will be huge gaps in the knowledge acquired through practice.

I like the idea of discarding the results of exploratory processes that GeePaw Hill elaborates very well. It removes the incentive of trying to reuse artifacts that were created "while learning" and just bring back the lessons learned.

Post reply on HN