[nonasktell]

"You don't have to know languages in order to be familiar with the concepts."

If you only ever coded in a language that doesn't even offer you the ability to tinker with some concepts, you can't be familiar with those. Reading one article about it without ever touching code, is not being familiar with a programming concept.

I'm not saying you should know 10 languages, but if you want to be anything more than a frontend dev or a bad web dev, you need to be exposed to more than 1 language IMHO. I'm not saying you should be an expert, or used multiples languages for years, but at least trying other languages with concepts not available in your favorite language.

[hardware2win]

>but if you want to be anything more than a frontend dev or a bad web dev,

Ive jumped from web/desktop dev

to semiconductor industry and worked with the same language.

And the biggest problem was lack of the domain knowledge, not langs.

You can find various langs being used in various places to the point that sometimes you'd be shocked

[tester756]

>If you only ever coded in a language that doesn't even offer you the ability to tinker with some concepts, you can't be familiar with those. Reading one article about it without ever touching code, is not being familiar with a programming concept.

I disagree, you're familiar by definition.

You're just not experienced and may be not aware of pros and cons unless the article/book/w.e showed them.

Whether experience is important is up to the thing you're talking about.

For example: stealing Result<T> from other language to replace exceptions in your language doesn't require you to use Result<T> impl. in other lang.