I'm a dev with a strong *NIX sysadmin background. I've been programming for 20+ years, started with IRC scripts, C, Python, PHP, Ruby/Rails, Node/JS, Go and Elxir. Full time on Ruby,Elixir and Rust.
20 years ago I liked *NIX a lot (and I still do!), I learned it for fun, but when I was looking for a job, it turned out it was useful even for profit. Back in the days, at least in Italy, there was a shortage of decent Linux system/network admins. So it wasn't difficult to get a job.
Then I felt that the field was too overcrowded and, after all, it wasn't so funny as in the first days, once you learned some tricks and gained some experience. Also, wages became lowering, time to switch.
I've always loved programming too, so I switched to full-time developer. I used mostly C and Python (from my sysadmin days) and PHP for web development (along with JS on the client side), but I hated PHP, especially after I discovered Ruby. But Ruby was very niche (or at least it was exploding in popularity in USA, around 2006-2007, not in Italy for sure). So I embraced Ruby: it was fun and very fast to write programs, BUT in Italy was barely known. So I kept learning Ruby/Rails while still working with PHP. At some point I eventually decided to work only in Ruby. Today a lot of job offers are looking for Rubysts.
10 years later, I did the same with Elixir and Erlang, for the same reasons.
An so on :-) Choose something you (would) like to use/learn, not too much overcrowded and that adds something more to your toolbox (skills, programming patterns, experience, tools, whatever...). That way you'll always be on the bleeding edge, well paid because rare to find. And when it will be more popular, in the worst case, you'll have collected several months/years of experience :-)
Choose something you (would) like to use/learn, not too much overcrowded and that adds something more to your toolbox (skills, programming patterns, experience, tools, whatever...).
I'm a dev with a strong *NIX sysadmin background. I've been programming for 20+ years, started with IRC scripts, C, Python, PHP, Ruby/Rails, Node/JS, Go and Elxir. Full time on Ruby,Elixir and Rust.
If I wanted to find a job, I might be more worried about TCL's lack of modern appeal. Thankfully, I can just use it because I like it. Maybe it'll be cool again in 10 years! lol
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.
20 years ago I liked *NIX a lot (and I still do!), I learned it for fun, but when I was looking for a job, it turned out it was useful even for profit. Back in the days, at least in Italy, there was a shortage of decent Linux system/network admins. So it wasn't difficult to get a job.
Then I felt that the field was too overcrowded and, after all, it wasn't so funny as in the first days, once you learned some tricks and gained some experience. Also, wages became lowering, time to switch.
I've always loved programming too, so I switched to full-time developer. I used mostly C and Python (from my sysadmin days) and PHP for web development (along with JS on the client side), but I hated PHP, especially after I discovered Ruby. But Ruby was very niche (or at least it was exploding in popularity in USA, around 2006-2007, not in Italy for sure). So I embraced Ruby: it was fun and very fast to write programs, BUT in Italy was barely known. So I kept learning Ruby/Rails while still working with PHP. At some point I eventually decided to work only in Ruby. Today a lot of job offers are looking for Rubysts.
10 years later, I did the same with Elixir and Erlang, for the same reasons.
An so on :-) Choose something you (would) like to use/learn, not too much overcrowded and that adds something more to your toolbox (skills, programming patterns, experience, tools, whatever...). That way you'll always be on the bleeding edge, well paid because rare to find. And when it will be more popular, in the worst case, you'll have collected several months/years of experience :-)
It worked (and is still working) for me ;-)
In the spirit of this, I encourage anyone to learn the Tool Command Language and Toolkit.
It's really nice!
I always loved it ;-)
Unfortunately is too much a niche :-(
Too true. I missed its heyday 90s.
If I wanted to find a job, I might be more worried about TCL's lack of modern appeal. Thankfully, I can just use it because I like it. Maybe it'll be cool again in 10 years! lol