3 ms·
"I'm trying to focus not on what's hot today, but what I think will be a solid background in 5 years." - any tips?
by _random_ 12y ago
"I'm trying to focus not on what's hot today, but what I think will be a solid background in 5 years." - any tips?
- dozzie 12y agoData structures. Architecture patterns. Software packaging and deployment principles (actual methods change, but core idea stays the same). Communication and data exchange patterns in distributed systems. Good languages present in the market for quite long time (Lisp, Erlang, Haskell, Python).
- _random_ 12y agoThings that don't change basically. Makes sense.
- pedalpete 12y agoThe way I look at it is to not jump on every new thing that comes along, but try to keep on eye on what's growing and what people are excited about. For me, at the moment, that means Angular and Node. Four years ago it was Rails and Backbone. I'm keeping an eye on React, but am not ready to jump on that bandwagon yet. Lots of people may suggest Haskell, Scala, Go, Ember, React, etc. etc. and I may add one or two of those in the future, but at this point, I don't see enough broad interest in those languages to make it on my list yet. Keep an eye on job postings and you'll see trends in languages and frameworks growing.
- _random_ 12y agoAngular and Node are exactly fresh new things. I would say it is better to learn MVVM/MVC and Reactor patterns those respective frameworks are based on.