Nice one, it made me laugh :) I'm actually a JS/Node dev, but since you are primarily a backend guy I would suggest you to try out Go. It's super easy to learn, designed for concurrency, statically typed and compiled language. Well, it's a C like language but I guess you can't have everything :)
I don't think a have a COBOL myself :) or at least I hope I don't have one.
Engenheiro de Software/Desempregador do Futuro. Falo no @GarantidaPod sobre renda básica—universal, comunitária e pessoal. Antes: @UnicampOficial @StartupChile @VoceFiscal @agentofuser #UBI #OpenUBI
You're right that Go has heavy institutional support and a booming codebase that will have to be improved upon and maintained in the future, so it is indeed a good bet.
I'm leaning heavily towards functional languages though for my nights+weekends "everything but JS" time, so on the backend I'll probably go with Elixir.
At the moment I'm dipping my toes into Elm. I've decided I can't run from the frontend any longer, especially since I want to build my own products end to end.
I agree that the language is just a tool and metalearning is the real skill. But "fast learner" is a hard sell if you can't prove core competency on at least one technology.
And I think it makes it easier to show your work via open source packages, blog posts, etc. if you commit to one thing for the long run. I'm very prone to shiny object syndrome, so choosing to take some root helps balance out mastering with exploration.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice one, it made me laugh :) I'm actually a JS/Node dev, but since you are primarily a backend guy I would suggest you to try out Go. It's super easy to learn, designed for concurrency, statically typed and compiled language. Well, it's a C like language but I guess you can't have everything :)
I don't think a have a COBOL myself :) or at least I hope I don't have one.
The programming language is just a tool.
You're right that Go has heavy institutional support and a booming codebase that will have to be improved upon and maintained in the future, so it is indeed a good bet.
I'm leaning heavily towards functional languages though for my nights+weekends "everything but JS" time, so on the backend I'll probably go with Elixir.
At the moment I'm dipping my toes into Elm. I've decided I can't run from the frontend any longer, especially since I want to build my own products end to end.
I agree that the language is just a tool and metalearning is the real skill. But "fast learner" is a hard sell if you can't prove core competency on at least one technology.
And I think it makes it easier to show your work via open source packages, blog posts, etc. if you commit to one thing for the long run. I'm very prone to shiny object syndrome, so choosing to take some root helps balance out mastering with exploration.