3 ms·

10000 hours to mastery is what it takes, this is not new news However, everyone wants shortcuts, specially recent generations with short attention spans Do yo

10000 hours to mastery is what it takes, this is not new news However, everyone wants shortcuts, specially recent generations with short attention spans Do your 10k hours conscientiousnessly in a specific domain and you're automatically at a huge advantage in the current market

spacecadet 2y ago
10,000 hours also isn't that long in the grand scheme of things. I remember when I broke 10,000 in the arts, then 10,000 writing code, and so on, I dont even keep track now.
kragen 2y ago
'10000 hours to mastery' is incoherent bullshit. 10000 hours to mastery of programming? to mastery of programming numerical methods? to mastery of programming gauss-seidel elimination? to mastery of programming sparse gauss-seidel elimination on vector supercomputers? to mastery of programming sparse gauss-seidel elimination on vector supercomputers for fluid mechanics? if your first 10000 hours were in c++, do you need another 10000 hours to get to mastery of programming sparse gauss-seidel elimination on vector supercomputers for fluid mechanics in fortran? at most one of these can be correct for a given level of mastery and for a given person (and that's not even getting into variations between people) like most things gladwell made up, it sounds good at first but falls apart the moment you think about it for a second
paulpauper 2y ago
It is wrong and was debunked. Some people need far fewer than 10k and others never become good no matter how long. There so much variability it is useless as a heuristic.
MiscCompFacts 2y ago
It’s not just “10000 hours”, it’s deliberate practice that’s necessary for mastery. You must first identify the expert skills before practicing and work problems in those domains where you are lacking. Here’s a video on this exact subject: https://youtu.be/WbUOY9ioIqw?si=a60ILLODGDEU7_CA https://youtu.be/WbUOY9ioIqw?si=a60ILLODGDEU7_CA

spacecadet 2y ago

10,000 hours also isn't that long in the grand scheme of things. I remember when I broke 10,000 in the arts, then 10,000 writing code, and so on, I dont even keep track now.

kragen 2y ago

'10000 hours to mastery' is incoherent bullshit. 10000 hours to mastery of programming? to mastery of programming numerical methods? to mastery of programming gauss-seidel elimination? to mastery of programming sparse gauss-seidel elimination on vector supercomputers? to mastery of programming sparse gauss-seidel elimination on vector supercomputers for fluid mechanics? if your first 10000 hours were in c++, do you need another 10000 hours to get to mastery of programming sparse gauss-seidel elimination on vector supercomputers for fluid mechanics in fortran? at most one of these can be correct for a given level of mastery and for a given person (and that's not even getting into variations between people) like most things gladwell made up, it sounds good at first but falls apart the moment you think about it for a second

paulpauper 2y ago

It is wrong and was debunked. Some people need far fewer than 10k and others never become good no matter how long. There so much variability it is useless as a heuristic.

MiscCompFacts 2y ago

It’s not just “10000 hours”, it’s deliberate practice that’s necessary for mastery. You must first identify the expert skills before practicing and work problems in those domains where you are lacking. Here’s a video on this exact subject: https://youtu.be/WbUOY9ioIqw?si=a60ILLODGDEU7_CA https://youtu.be/WbUOY9ioIqw?si=a60ILLODGDEU7_CA