avoid procedural knowledge until necessary
procedural knowledge takes a lot of time to build.
ex: it may take you 50 hours of practice to learn how to juggle a soccer ball.
declarative knowledge on the other hand, can be learned very quickly (if you use the correct techniques).
you can get very far on just declarative knowledge.
one important step is to build process notes that you follow.
be wary of trying to master topics that require lots of procedural knowledge, because it can be a huge time waster.
ex: i know it will take 10,000 hours of practicing with a basketball to be NBA-level. so i would be very wary of making that decision.
ex: however, being a great conversationalist is a procedural knowledge topic that i think is worth 10,000 hours of “practice”. and so i do that.
applications
ex: you want to learn how to make good music.
- option 1:
- learn to play guitar, learn piano, learn drums, etc. (procedural).
- then learn music theory, song structure, etc.
- option 2:
- learn music theory, song structure, etc.
- type in the notes as midi on a computer. or sing it out with your voice (an instrument you already know).
you can improve much faster with option 2. basically, by mastering the declarative knowledge of the subject, and then using cheap tricks to hack the need for procedural knowledge, you can get much further, much faster.
procedural knowledge takes a lot of time to build.
- ex: it may take you 50 hours of practice to learn how to juggle a soccer ball.
declarative knowledge can be learned very quickly if you use the correct techniques
you can get very far on just declarative knowledge.
be wary of trying to master topics that require lots of procedural knowledge, because it can be a huge time waster.
- ex: i know it will take 10,000 hours of practicing with a basketball to be NBA-level. so i would be very wary of making that decision.
- ex: however, being a great conversationalist is a procedural knowledge topic that i think is worth 10,000 hours of “practice”. and so i do that.