3 ms·
Imho this is not a useful categorization. You can learn by doing, or by theory and then doing. The point of the theory is to take a compressible space of learn
by renewiltord 4y ago
Imho this is not a useful categorization.
You can learn by doing, or by theory and then doing. The point of the theory is to take a compressible space of learnings and compress+cache them. A principle or law or whatever is just a cached compression of a model of reality.
It has all the benefits of compression: you acquire the knowledge faster.
It has all the disadvantages of caching: your knowledge may be out of date.
There is nothing inherently valuable about a "conceptual" understanding or understanding the "fundamental principles" of something. All the value comes from the fact that the alternative is you can slowly build your model by experiencing reality bit by bit, constantly trading off use of your knowledge for building more knowledge. Or you can accelerate that process by downloading precomputed indexes from other people: what we call "concepts" or "principles".
With this model of knowledge, you can see that so long as you can extract commonalities from experiences (using your inductive reasoning faculty to generalize from small samples) you will capture "conceptual" models. This model also permits you to choose when you should choose to learn "concepts" and when you should choose to acquire the raw uncompressed experience: prioritize the compressed cache when it is likely to not be stale and it is likely to cover a wide knowledge space.
A heuristic for this is for fields that haven't changed very much in a long time. e.g. basic Physics has not changed in a long time. Reading the compressed model is superior. On the other hand, cross-platform UI development is a new field. You will be better served by trying something.
Another heuristic is the search cost. Using your inductive reasoning requires some examples. Areas where these are hard to acquire should move you to acquire through reading the compressed model. e.g. studying epidemiology is better served by reading through the state of the art in the field. On the other hand, you don't need to study principle to determine if one way to play a level in a videogame is superior.
A third heuristic is how large the search space is. e.g. Your musical tastes are constantly changing, and it's trivial to play the piano. However, the space of notes that sound pleasing to you are likely a small fraction of the space of notes that you can play on the piano. Here you will be better served learning some principles to cut the search space down.
P.S. By the way, to the author, you may benefit from running your posts by some English-fluent friends to proof-read. It is unlikely you meant to use "gives more inside".
- commandlinefan 4y ago> You can learn by doing, or by theory and then doing That's true, but I felt like he was getting at something else, though. I've met (and worked with) programmers who tried to stumble through everything by looking for a solution to the problem immediately in front of them, solving that immediate problem as basically as possible, and then working on to the next problem. They don't really understand how things like, say TCP or SSL or even HTTP work. They don't understand how their IDE relates to their compiler. They don't understand machine learning well enough to recognize when or how to normalize data. They usually expect somebody else to come along and "help" them with all of this stuff in a "just-in-time" way. I remember attending a Java user group one time when Hadoop was relatively new and the speaker was presenting it. He was talking about some of the challenges they faced getting it up and running and a woman interrupted with "but whenever you had a problem, couldn't you just google the error message?" He said, "there usually weren't any error messages and even when there were, google didn't find anything". She seemed shocked and actually argued with him a bit in disbelief. I was dumbstruck that here was a woman who was actually working as a professional programmer deep enough that she was attending Java user groups who couldn't conceive that there even could be problems that required enough fundamental understanding that "googling an error message" wasn't going to help.