Tired of learning new languages every few months. Where am I going wrong? Asking for a friend

As in... New programming languages? If you know more than 2, they shouldn't be "new" so much anymore. They all express the same logic, sure some in different ways, so maybe you need to pick up a new paradigm.

But sounds like you're bored of the work you're doing, more so than how you're doing it.

Theres no reason to learn languages all the time. Choose a few and master them

@atheist Unless you are learning HTML, CSS, JS...

@c3r38r170 aka a "different paradigm"? Even then, if you've written some java and UI code, it's not *that* different.

@atheist you’re right, just more annoying

Like @TeachMeCode, don't learn languages all the time. Choose a primary language that you will use it in nearly any project you make/contribute, and a secondary one that is very different from the primary language (like Python as the primary language and Rust as the secondary language).

Learning new language is fun but every few months sounds a wrong. You won’t be getting much experience in any of them at that rate

@atheist I was just considering the edge case of a frontend bootcamp for beginners.

…. this feels so alien. Only one new language a month? Where’s the fun in that when you could take on more?

If you are new in web dev, you might not get around learning some HTML, CSS, JavaScript for the frontend and another dynamically typed language and some SQL dialect for the backend.
If you are also doing "devops" you additionally have to know some server software configurations and some system scripting language (most often bash, but you can also do it in Python nowadays).

If you are a job hopper, you also have to learn the languges the old stuff has been written in - or can select jobs to match your skills...

You will be a classic “hello world” dev 😂😂

If you're burning out, stop doing it. No sane job requires you to learn new languages at that rate. Plenty of people I know have been using the same language in their role for a decade or more.

Learn one language *really* well, then get a lot of experience in that language, and become a specialist.

@atheist While I agree with the sentiment, any language I touch immediately gets me labelled as a Typescript or JavaScript dev because I don't hold the purity of functions sacred but I overuse lambdas and I'm comfortable with generic metaprogramming.

@lbfalvy sounds like you should learn c++.

@atheist I tried, but C++ also has lambdas and they can hold references to mutable state, and there's also the Turing complete template language so I don't see how it would solve any of my problems (other than that it forces me to have a clear idea of ownership relations in order to describe my allocations with smart pointers).

@atheist Or are you suggesting that I learn C++ because the style I've described would be tolerated there?

@lbfalvy I was thinking c++ because these days it's moving towards lambdas/generic programming, but with real type safety. I've seen some pretty wild styles tolerated. I've worked on a full functional code base (real time video processing multithreaded) in c++, sounds like you'd have enjoyed it. some generics/metaprogramming to generate resolution specialisms.

@atheist That sounds exciting, I'll see what it's like now.