Imposter Syndrome in Diagrams
jen chan
・1 min read
We're a place where coders share, stay up-to-date and grow their careers.
jen chan
・1 min read
Megan Lo -
Rajat Gupta -
Elijah Trillionz -
Dhruv Panchal -
Discussion (8)
I think the "10000 hours" thing has been debunked. And I like the "Are you my mentor?" cartoon :)
You still need 10,000 hours to achieve mastery, but you only need around 20 hours to be good enough to be a pro :)
I aspire to be mediocre. The rest will work itself out! 🤪
So maybe this is a sign-- I just got 169 "Proficient" on pluralsight. If I count on and off the hours spent reading/learning/fiddling... If I spend even 20 hours a month learning... 960 hours is a generous estimate for something I started since 2014 and had a million other life/stagnating full time work/health things going on.
Been coding for 20 years and still feel like I'm barely hanging on. TDLR, I'm doomed. So much tech out there to work with and that changes so frequently, often less than 10K hours before a new framework is introduced and have to adapt to. Better off being a jack of all trades and knowing how things generally work together to sustain mediocrity ;)
if I manage to get to mediocre, in about 10 years I'll switch into management (after seeing my ex get carpel tunnel), but I hear that requires being brilliant.
If you count 4h a day of focused study/practice and 5 days a week of work, that's 10 years. I think that it's reasonable to call somebody a pro with a lot of experience and depending on one's commitment, you can say that the person is an expert.