It's good to identify what you don't need to bother learning
Ben Halpern Nov 8
This thread has a lot of great answers:
I tried to comment, but was not able to really put my finger on the stuff I'm not interested in learning. Instead I simply read, and I believe there is a lot of wisdom in some of these answers. Enjoy!
The modern frontend toolchain is where I'm tapping out on the "full-stack" idea. I can do everything I need to do with server-rendered templating languages; if I'm working on something that requires getting serious about understanding React or Vue or Webpack, I'm going to be working with someone who knows React or Vue or Webpack. I can work out what's going on in there well enough to fix problems and add minor features, but I'm profoundly disinterested in digging deeper.
Machine Learning. I see it thrown around everywhere as the new thing to do, and I just can't build up the energy to dig into the complexities (both with the science behind it and the massive amount of different libraries available).
VIM and DevOps are actually on my current list haha, although that's also on the advice of my current manager. My own list includes:
- Virtual Reality
- Additional backend langauges other than Ruby (part of my current job)
- Arduino or Raspberry Pi
I want to include calculus as well, but my manga book on Calculus always pulls me back in.
the list could be endless if I start adding things like SAP :D
These are the things that pop in my mind right now:
blockchain: I'm honestly totally bored to death everytime I hear someone mention "blockchain". It's not rational, I just tune out. Probably my subconscious is trying to protect me from the hype
kubernetes: super useful, just not particularly interested. More interested in what comes next, I need one more level of abstraction
AR/VR: reality is way more interesting for now :D
internet of things: except real sensors in urban environments... why are we doing this to us?
hardware: I don't remember the last time that I built a computer. Probably in high school. I keep a distant eye on what's going on in storage and memory advancements though.
AI/ML: turn down the hype. Learning something about ML is quite useful though
PHP/Wordpress/Drupal: I know, I know. I shouldn't judge a book by its cover
DevOps. BlockChain. Angular.
It's really hard not to fall for shiny object syndrome, so I think you really have to keep that focus in mind of what your goals are for being a developer <3. Thanks for posting this, as always ali :)
The things you have on the list are on mine as well.
Not so long ago I wanted to learn everything and thought it is possible. Some job descriptions made me feel that I need to know everything. Now I know better - there is too much and I need to specialise to achieve any notable results and satisfaction from my work.
Everything else is not on my "to learn list" at the moment.
The thread has a lot of other great answers I didn't highlight. The point is that managing your own expectations and being okay with the fact that you'll never learn everything is important.
Nobody is telling you that you can't change your mind later, but it's okay to fall behind in certain areas of software development while going deeper on others. Managing this interplay is important for your career evolution.
Here is a somewhat related post, addressing the other end of the generalist-specialist concern:
Happy coding ❤️