DEV Community

Discussion on: 10,000 hours...?

Collapse
 
iamntz profile image
Ionut Staicu • Edited

Gladwels's 10.000 hours is a misinterpretation from a study of Anders Ericsson.

The gist is that you don't need only 10.000 hours, you need meaningful practice to become a master.

The reality, however, is that you don't always need to become a master in your field (ok, you're mastering JS, but what about your editor? your version control? your X or Y?), but you need to be proficient.

And that's slightly more achieveable.

This is a nice video on this subject:


From your list, this one poped out:

I've read half of "clean code" and I understood about 95% so far!! 5 hours

If you have next to zero experience, I'm pretty sure you didn't understood 95% of what you've read from Clean Code. Also, is not really a book that I'd recommend you if you don't have enough experience with not-so-clean code.


To answer your question: if you get past understanding language structure (variables, scopes, functions, recursion and so on), stop following courses and start building stuff. Usually creating a clone of a popular app (e.g. Facebook, Reddit) would teach you a LOT more than a course can.

Following introductory courses will only give you a false sense of accomplishment, but in the end you get close to nothing.

Collapse
 
beitist profile image
Sebastian Stüwe

Ionut - thanks for your insight. I wasn't aware of the misinterpretation, but it does make sense, I'd say, in particular when you apply it to something that is not an isolated skill.

I will take your advice and work on realistic projects. I have a million ideas and it is quite tempting to follow all those "learn me now!" blogs and vlogs and courses, but it's not for the learning in itself. Thanks!

Collapse
 
iamntz profile image
Ionut Staicu

is quite tempting to follow all those "learn me now!" blogs and vlogs and courses

At best, you'll get amazingly good at... copying stuff. Monkey see, monkey do.

I think that's easy to fall into tutorial porn and follow blindly everything, but the endgoal should be „be good at doing/creating/fixing stuff”.

Problem solving skill is just like a muscle: you have to train it over and over again to get better.

What do you think would be more beneficial in the long run (you don't have to answer me, you have to answer yourself):

  1. copying (or even worse: copy/pasting!) from a video/book by following a tutorial step by step OR
  2. trying to come up to solutions you don't even know you'd have?
Thread Thread
 
beitist profile image
Sebastian Stüwe

Makes a lot of sense, Ionut, and I love your direct language! tutorial porn is definitely a term I'll add to my long-term memory.

And the implicit answer is obvious. :-)