The Node.js job market
blog.8020.co
blog.8020.co
http://www.indeed.com/jobtrends?q=javascript%2C+objective+c%...
http://www.indeed.com/jobtrends?q=javascript%2C+java%2C+node...
Slight nitpick, but I noticed Javascript and Node.js n the same charts, Node.js is Javascript and Javascript is Node.js.
"If your concern is finding a tech job then your trusty existing technologies are continuing to serve you well." — this statement made me laugh. Any sane technical director/lead knows better than to make a business rely on something still so new. Node.js has proven itself to an extent, but it's got a long way to go before people start using over the likes of Python or .NET.
I've used Node.js a little bit myself, but mostly only when hacking on an idea, not for production use. At the end of the day, use what you like and build what you love.
Here is some salary data on it. http://www.payscale.com/research/US/Skill=Node.js/Salary
I've got to run to a meeting, but I'll see if I can find more details when I get back
I just find it strange that as a JavaScript developer, many recruiters (and even some companies) won't even consider me for a Node position unless I explicitly state that I have Node experience.
There's also JavaScript developers who are only interested in front-end development, and for them it's a good way to let them know what to expect.
In reality it's not different from asking for Swing developers vs. general Java skills.
What is "the Node way"?
I love node, btw!
I can only really think of two patterns I see in node.js that I don't see everywhere else: eventemitter and chaining middleware together with next() calls. Hardly something it takes 5 years to learn. ;)
Well, they're specific to Node and therefore have to be learned, to some extent.
There's also a million other things, some little some big. Little -> knowing that the first argument of a callback is an error. Big -> Understanding Streams. Medium -> the use of small modules, knowing when to break up a file into smaller modules, knowing when to break up a project into many modules, etc.
Also, there's just some stuff you know when you're working with Node all day. Same thing with every profession and specialities. If you work in Rails all day, your'e going to know a hell of a lot more about it than me. I can't just pick up what you know in a weekend.
This is an example of a node-ism,
if (err) { return err } console.log("KEEP GOING")
Notice how we break from an error right away. As a Node developer, you may not use the pattern, but you're definitely aware of it. Someone with just JS, and let's be honest, jQuery, is not used to returning quickly if there is an error. Decorating and animating a UI is far more forgiving.
I's not about how long it takes to learn a certain module. It's about mitigating risk in building large web apps.
I mean it isn't like we'd stop them from using node for things, just that they'd have a lot of other stuff to do.
What this graph really means is... "How many job descriptions contain the term ...". And that's about it.
realistically, unless you're part of a startup where the primary technology stack has yet to be defined, finding paid work in node isn't all that common.
http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
Hipster brogrammer wanted. Lack of knowledge of other languages wanted. Thinking every part of the tech stack should be written in JS. Must create yet another layer of shit to translate into JS and pretend it is cool! Must be willing to run to the next shiny-shiny when released and be willing to abandon current projects.
Amazon, Microsoft, Apple, Expedia, Staples, Nordstrom, Macy's, Disney, Hulu, Comcast, T-Mobile, AT&T, Getty, LinkedIn, Heroku, Oracle, eBay, AOL, E*TRADE, Yahoo, Walmart, Sony Computer Entertainment, Lockheed Martin, GE, HP, MLB
Glad I don't work for any of THOSE jerks!
/sarcasm
.NET being more of an enterprise technology, I'm not surprised that the first step would be for HR to make job postings on Indeed or other sites. With Node, I don't have the same impression of it being accepted in the enterprise yet (though MS is pushing it with Azure, for instance), and it's also such a young technology that not too many organizations are hiring maintenance developers for legacy projects yet.
The relative trends chart is exceptionally misleading.
Kaggle - San Francisco, CA We're hiring our next Software Developer - Web Platform (C#, ASP.NET). REMOTE within US timezones or E3 is a possibility for the right candidate.
Kaggle runs data competitions that solve business problems for companies and provide fun and prize money to the world's community of data scientists. We're offering an opportunity to be involved in what Forbes magazine called the most novel Machine Learning applications that are "eating the world" [1]. As a developer, you'll be responsible for keeping kaggle.com (and the 140,000+ users who play there) running: everything from front-end UI work to server-side code and DB architecture.
See https://www.kaggle.com/careers/ to apply and learn more about our team.
You may want to use regex to find more. Hope it helps.
If all I get out of it is increased javascript skills and linux familiarlity, then it'll be time well spent.
My current shop is .net/windows, but in the last couple years we've introduced nginx, python (django), and angular. Times they are a changin'.
Also, there seems to be quite a lot of confusion about node.js around recruiters/job postings. It is often being treated as another *.js library and put under front-end category.
http://www.asp.net/mvc/tutorials/mvc-4/bundling-and-minifica...
It's always funny when technology hipsters are surprised that the wider world doesn't share their anti-MS biases.