61–70 of 273 posts
Best strategy for becoming a high paying/good software engineer would be to think of yourselves as problem solver and language as just one of the tool for problem solving. Thinking of yourselves as someone who is a writer of a certain programming language is self constarining and missing the point.
Seems like there’s a lot of listings if you just Google “elixir jobs.” There are also a few dedicated sites such as https://elixirjobs.net/
Non-existent to a close approximation (maybe more Elixir stuff out there than the others you listed but still very rare). Learn those languages if you’re interested and curious but if the goal is to get a job with a new to you language, stay as far away as possible from them. Not only are there very few jobs but also the niche languages will distract you from learning stuff that’s in demand.
If you go looking for elixir stuff it’s there, and it seems like its usage in industry is expanding at a steady pace. IMO this is because it’s a reasonably approachable language designed to solve a common difficult problem (high concurrency, fault tolerance at scale)
It is better to pick languages based on platforms than the other way around.
I mean, what don't you like about JS? Is it the syntax or is it the environment? The code base? The framework? Maybe web dev is not for you? Maybe you are asked to do thing you personally disagree with (ex: ads). Language rarely was the main thing that defined the project, though there are correlations: if you are doing JS, you are probably doing web dev, with a higher chance of front-end work. But chances are that a NodeJS back-end and one written in, say, Elixir, won't feel much different after the honeymoon is passed.
If you want something different to JS, why not try good old C instead of niche languages? It has a significant job market, you will learn about memory management, and get your foot into embedded, high performance, and system programming, far from the world of JS. These skills will translate into the other (niche or not) languages you may use next. Even in high level languages, having an idea of how that works on a lower level is a good thing.
What is it about js you dont like? is it really about the language? a lot of the complaints i hear about js have more to do with “the community”, “the team”, “the application”. here’s the thing: there is _so much_ built in js. i think theres a better chance you find what you want in a mainstream language (js or otherwise), but you first have to identify what your values are.
Best strategy for becoming a high paying/good software engineer would be to think of yourselves as problem solver and language as just one of the tool for problem solving. Thinking of yourselves as someone who is a writer of a certain programming language is self constarining and missing the point.
I used to think this way and wound up completely exhausted in my career. Coming from web dev, I used to volunteer to dive into a Objective C repo to fix some random bug in a mobile app and then a week later my boss would ask me to build a big feature in that app. I'd spend a few weeks getting up to speed on the language and build the feature, and then I would never use what I learned again. My boss would ask me to di…
There is power in saying No.
There is a significant Erlang/Elixir job market in Europe and UK.
PG has a really old (2004) blog about how python programmers are smarter than other programmers. Basically it comes down to the python programmers being ahead of the curve by learning a less popular language (at the time), and they must be using python because they believe helps build better software or whatever. Meaning they're less likely to simply be 9-5 programmers just doing it for the money, but will have opini…