I'm still reading the article, but I stopped halfway to point this out:
Remember the ‘10,000 Hours’ Rule for Success? Forget About It
They should not have said that. I don't know whether 10K is the actual number, but I got good at two things that I was never naturally good at, simply through years of brute force repetition: coding and writing.
I was never a born hacker -- I struggled with Visual Basic when I was 21. But 15 years and maybe 300,000 lines of code later, I have an extremely high degree of proficiency in both C++ and JavaScript, with a good level of proficiency in Java, Python and Golang. I was extremely bad at writing. So much so my fingers used to sweat when I came to the essay section of any test. But after about a decade of keeping a personal journal, I would like to think I write rather well.
Anecdotal yes, but speaking personally, I would not discount the 10,000 hours concept.
Remember the ‘10,000 Hours’ Rule for Success? Forget About It
They should not have said that. I don't know whether 10K is the actual number, but I got good at two things that I was never naturally good at, simply through years of brute force repetition: coding and writing.
I was never a born hacker -- I struggled with Visual Basic when I was 21. But 15 years and maybe 300,000 lines of code later, I have an extremely high degree of proficiency in both C++ and JavaScript, with a good level of proficiency in Java, Python and Golang. I was extremely bad at writing. So much so my fingers used to sweat when I came to the essay section of any test. But after about a decade of keeping a personal journal, I would like to think I write rather well.
Anecdotal yes, but speaking personally, I would not discount the 10,000 hours concept.