3 ms·
I speedcube, and deliberate practice is extremely important. I also code, and deliberate practice doesn't do much in that area. I need to have a feel for the c
by rpmisms 5y ago
I speedcube, and deliberate practice is extremely important. I also code, and deliberate practice doesn't do much in that area.
I need to have a feel for the code, understand what chunks of code do without having to read every line. That's tacit knowledge.
Maybe the difference could be explained with racecar driving. Driving the track correctly, hitting apexes, downshifting at the right moment; that's deliberate practice.
Knowing your car, understanding what a particular vibration means, feeling when you're approaching your traction limit, knowing that your engine is weak from 4-5k RPM, that's tacit knowledge.
Deliberate practice can foster tacit knowledge, however. Going through the motions opens your mind up to understanding what's going on behind the relatively simple task you're performing.
- Jensson 5y agoYou can do deliberate practice for technical creativity, I do it all the time. You basically take any problem, like "How to build a server", and instead of looking up guides on how to do it you just start breaking it down. So a server needs to connect ot other computers, so you go and figure out how to make such connections, and then how to make multiple connections in parallel, then how to listen to connections etc. And soon you will have a working server. That was how I learned programming. It is slower and more tedious than just looking it up, but it is good deliberate practice for getting more technically creative. Looking things up doesn't teach you much, figuring things out yourself is how you practice things in this domain. Deliberately not looking up solutions to known problems is like a super power, you don't want to spoil yourself there you can only figure things out before you have seen how it is done after that you just recall the solution.