For further actions, you may consider blocking this person and/or reporting abuse
Read next
Megalodon: Efficient LLM Pretraining and Inference with Unlimited Context Length
Mike Young -
ResearchAgent: Iterative Research Idea Generation over Scientific Literature with Large Language Models
Mike Young -
The Illusion of State in State-Space Models
Mike Young -
Promices and Async Await
Rohit -
Oldest comments (5)
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.