---
title: "Comment by Mario Giambanco on \"10,000 hours? Nope. Learn something new in 20!\" | Hashnode"
description: "Everyone&#39;s capacity to pick up a new skill is going to be different. IMO 20 hours is not enough to be proficient in any language, let alone JS. I would comp"
url: "https://hashnode.com/posts/10000-hours-nope-learn-something-new-in-20/5eada36f26e78ca711dfc2c8/comment/5eb02823f89d4c762e706a6a"
---

[Discussion](https://hashnode.com/posts/10000-hours-nope-learn-something-new-in-20/5eada36f26e78ca711dfc2c8)

Comment [10,000 hours? Nope. Learn something new in 20!](https://hashnode.com/posts/10000-hours-nope-learn-something-new-in-20/5eada36f26e78ca711dfc2c8)

[Mario Giambanco](https://hashnode.com/@mgiambanco)

[May 4, 2020](https://hashnode.com/posts/10000-hours-nope-learn-something-new-in-20/5eada36f26e78ca711dfc2c8/comment/5eb02823f89d4c762e706a6a)

Everyone's capacity to pick up a new skill is going to be different. IMO 20 hours is not enough to be proficient in any language, let alone JS. I would completely ignore a resume that said anything like 20 hours of education.

Learning / getting good at a programming language is a life style. You don't need to live and breath it, but you need to work at learning it day in day out. This is why it tends to be easier to learn things on the job. You have a built in 40 hours / week commitment to learn it.

Further - learning a language doesn't mean you're good at it. Anyone can rattle off methods and functions built into a language. What makes a good programmer is the ability to take those things you learned and build stuff or talk intelligently about it. When the boss asks "how would you approach X problem" the difference between answers from someone with 20 hours and 10,000 hours of experience will be night and day.

Good programmers bring their years of experience with them to a problem / job and 20 or 100 hours just won't cut it. Being a problem solver is so much more important than memorizing the syntax for a language.

[Emil Moe](https://hashnode.com/@emilmoe)

[May 5, 2020](https://hashnode.com/posts/10000-hours-nope-learn-something-new-in-20/5eada36f26e78ca711dfc2c8/comment/5eb02823f89d4c762e706a6a#reply-5eb134da352b69972eb68f0b)

> Practice for at least 20 hours. To overcome what Kaufman calls the “frustration barrier” — that period in the beginning when you’re painfully incompetent and you know it — you must commit to sticking with your new activity for at least 20 hours. By that point, he says, “you will be astounded at how good you are.”

And what he basically says is that every skill takes 20 hours. So to understand `if-then-else` expect 20 hours, to understand `public / private` expect another 20 hours. So I agree with you and 500 of these sums up to 10,000 hours which is, by the way, researched by Malcom Gladwell and a well argumented in _The Tipping Point_.
