> There's a question of: If you know 20 programming languages, how well do you know any of them individually?
The real question is how well should you know each individual language to be productive?
Is knowing dark corners of some obscure language bears more value (in terms of productivity) than an ability to chose the most fitting language for your particular task you're doing at the moment?
And when I mentioned dozens of languages, I was talking about the DSLs primarily. A well-designed DSL does not need much learning effort at all.
> Library knowledge, beyond a certain point, is far more important than programming skill.
This must be very dependent on an industry you're in. Enterprise Java coding - maybe. HPC - partially true. Embedded - what libraries?!? Can't find any!
The real question is how well should you know each individual language to be productive?
Is knowing dark corners of some obscure language bears more value (in terms of productivity) than an ability to chose the most fitting language for your particular task you're doing at the moment?
And when I mentioned dozens of languages, I was talking about the DSLs primarily. A well-designed DSL does not need much learning effort at all.
> Library knowledge, beyond a certain point, is far more important than programming skill.
This must be very dependent on an industry you're in. Enterprise Java coding - maybe. HPC - partially true. Embedded - what libraries?!? Can't find any!