@MadcapJake
Perl 6 & JavaScript full-stack developer
I'm a self-taught programmer who loves the variety and diversity of programming languages. My current favorites are Earl Grey, Perl 6, Mozart 2, and Nit. I also am experienced with Python, JavaScript, Racket, Clojure, Ruby, and Standard ML. I'm interested in learning Rust, Nim, Ark, and anything else new and fresh!
Lately I've been developing Perl 6 plugins for Atom Editor, a Gnome HIG-influenced terminal emulator called Tattoo, and a Electron-based IDE for Nit.
Nothing here yet.
No blogs yet.
I start by finding and assessing tutorials based on amount of content and hopefully there's at least one tutorial that seems to cover a lot of bases and also isn't too handwavy. Then I follow along, writing everything out by hand. All the while, testing various tweaks and changes. (Make sure you've installed idiomatic/popular tools and use them right away to really get acclimated to the language's workflow) After I'm done with the tutorial, I first take a look through the language reference and read various bits and pieces, searching the internet for anything that seems interesting/vague to find more thorough explanations. Finally, I pick a small project to complete in the language. At this point you want to try writing most everything on your own, but don't be afraid to find a similar project and try and apply patterns/implementations in your own code. Often times this is the best way to see how others code in the language. One thing to note through all of these steps: just as with a human language, you need to immerse yourself in it! Discuss on IRC channels, get active in forums, contribute to open-source repos, find various ways to connect with others. You'll find that people will more readily help you if you are giving back to the community.
Despite the misinformed and mildly offensive remark about Angular 1.4, there really are tons of options available. For production-ready now solutions, my personal favorites are Mithril.js, Cycle.js, and Ember.js. However, I think the path of least-resistance would be to stick with Angular and follow the upgrade path to Angular 2.