hmmm ... imho. on the one hand: tools are tools, and there is a good reason for why there are a plethora of tools available in this (it) world. concentrating

hmmm ... imho. on the one hand: tools are tools, and there is a good reason for why there are a plethora of tools available in this (it) world. concentrating too much on one tool only reminds me of the "old saying": "if your only tool is a hammer, all problems look like nails". so personally i like to be T-shaped in my knowledge and build up "deeper" tool-related knowledge on demand in case it matters. on the other hand: software-development is a meta-understanding game, writing actual code is only a small part of it. in a nutshell: understand the problem at hand, the additional value of the project for a customer, what are the use-cases for the customer, various patterns which are useful for solving a specific problem, academic approaches vs. real-world solution etc.etc. getting to know different approaches to programming - languages and their surrounding tool-ecosystem - serves as a source for different viewpoints on problems -> and increases the level of insight of a software-developer. idk ... just as a quick example "imperative" - procedural, oo - vs. "functional" etc.etc. comes to mind if we talk of language concepts. cheers t.