> I also find that whole "I can code in 12 different languages" a bit shallow. It's 83 in my case... (I'm joking: obviously I didn't write much code in most me

> I also find that whole "I can code in 12 different languages" a bit shallow. It's 83 in my case... (I'm joking: obviously I didn't write much code in most mentioned languages. But I wrote at least something in the 100-1000 loc range in most of them, I think). > Have I mastered those languages, or am I just surfing the shallows of each, unable to get the most out of them? That's only a question you ask yourself at the beginning. You stop doubting your skills and knowledge in different languages around a decade into learning about them. Well, that's how it worked for me. > and it seems that my time would be better spent practicing more javascript (10,000 hours and all that). Been there, done that (metaphorical 10000 hours). Four times over with C++, PHP, Python, JavaScript. Then Erlang, and after that, the time needed to learn most of almost any language was significantly reduced. > I'd prefer to pick, say, three languages, at most, and really learn them. Again, been there, years ago. Programming - for me - is a life-long career choice, which means I still have 3-4 decades of coding ahead of me. With a solid 10+ years of experience already I know that staying too long with one tech causes boredom; the issue is how to pick the next tech? I figured I'd need to learn quite a lot of them to make informed choices, and so I focused on this. I don't want to stay with a single tech for too long.