Why I'm Learning Nodejs
In software industry, if you are not updated you will be outdated1. So I continue to learn new stuff regularly. It has been a long, but interesting road from CLI to GUI, and FORTRAN to Objective-C.
This year(2014), I am learning nodejs. I got three reasons:
It’s an investment: When I say ‘investment,’ I don’t mean only direct financial gains. It’s too early to tell if I’ll develop commercial apps or not in node.js. But I’m sure that the lessons learned in developing, testing, deploying and maintaining node.js apps will have a broader application in my software career.
True to my consume-produce-engage learning framework, I’ve been watching videos and reading lots of articles on nodejs. As a next step, I’m thinking of building few apps to scratch-my-own-itch. It will either be a static blog engine or a URL shortener. I’m excited.
This explains why lazy programmers aspire to become managers. Nothing has changed in management in 50 years. Wrap the concept in a different terminology and you are good to go for years without another effort from you.
I was going to say, it gets me close to being a ‘full-stack-developer’, but as this O’reilly radar article says, there are no software unicorns, only T-Developers (“a developer with broad knowledge and interests, but who understands one area deeply”).