The most efficient way to learn Node.js is to do something with it. Nice of you to do the research first, very smart!
There are two approaches to this: 1) Try to build something "real". If you have prior programming experience, you'll know that the language has it's quirks. Watch Douglas Crockford "the good parts" if you haven't already, to figure out basic gotchas that will stop you, then go straight into a project. It doesn't matter what, as long as it's relatively simple. Maybe a simple website that displays a form or two and loads and saves this from the database, maybe a command line program that converts a .csv into an xml or json. Then build on that program, expand it or make a new one. Try to build something that you've already built with the language you're currently using. 2. Do some "boring work" first Still with Node, only focusing more on general programming concepts. I would recommend this if you didn't do any coding before. Take something like this list here (just something off of Google): http://www.programcreek.com/2012/11/top-10-algorithms-for-coding-interview/ Go ahead, try it, pick one and do it right _now_. And try to make two more today, and then another three tomorrow. (Granted, it's meant Java, but you can work on those things with JavaScript just fine. It will teach you a lot about syntax, and a about JavaScript specifics.) The first will get you a little closer to Node.js typical usage sooner. The second approach will teach you more about JavaScript sooner. But if you want to get good at any of this, you should know both JavaScript and Node.js specifics well. But the rewards? The reward is that you can, once you get good at it, deliver complex REST APIs in a week or two, something that would take three people 2 months until very recently, and even now it would take a lot in many other languages and platforms. The reward is that you feel the expressiveness of JavaScript, that you feel that you can take any library and bring it about and make it suit you just perfectly. The reward is that you can think much more about the problem at hand, then about which library to use and is it compatible with some other library. The reward is that even after years of Node.js work, you still feel excited like a kid on each new project because you get to try and learn new stuff. That's a humble advice that I feel would be good for myself, and I hope it also helps you. Zlatko On Tuesday, February 17, 2015 at 3:12:29 AM UTC+1, Kevin Bueno wrote: > > Ive done a lot of research, and I want to know what you y'all think? I > understand the advantages of already knowing JavaScript, but is it worth > the time to put into it? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/842ba8c6-9212-496a-8cfb-82d8817a27fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
