angular-seed

Kind of surprised how in depth the tutorial goes, but only manages to mention the word "test" once and doesn't cover the fantastic testing back end included with the AngularJS seed (https://github.com/angular/angular-seed). Unless the person learning AngularJS has never done any automated testing before, I can't see any reason why not to be using tests as a tool to further your own learning. I learned Go last year relying heavily on tests, first specifying what I wanted to achieve in a high level test, then learning as I figured out how to make the test pass.

Batarang[0] is chrome plugin that vastly helps with debugging angular. I also highly recommend approaching it from a TDD standpoint. The seed[1] project comes with a baked-in testrunner. This also helps you move away from direct dom manipulation unless absolutely necessary: treat it like the definition of an html DSL specific to your app. 0. https://chrome.google.com/webstore/detail/angularjs-batarang... 1. https://github.com/angular/angular-seed

If you need to use multiple files (and let's be honest it's better that way), I recommend you try RequireJS. It's pretty simple, remove ng-app from your body, and add the following to you boot.js: https://gist.github.com/4600740 Alternatively, if you need good boilerplates with multiple files and proper organization: https://github.com/elsom25/angular-requirejs-html5boilerplat... and https://github.com/angular/angular-seed .

I'm very excited to try Angular. Your tutorial, however, is not compatible with the suggested server experience where Apache is not installed, as Node has updated to v0.8 and not only deprecated but removed the "sys" module in favor of the "util" module. Update your repos please? https://github.com/angular/angular-phonecat/pull/18 https://github.com/angular/angular-seed/pull/22 Not digging against you, but this might (though, imho it shouldn't) be a barrier to entry to newcomers. I've simply resigned myself to editing the one line it takes to complete the tutorial every step of the way... Though in retrospect I think I probably could have just forked it and updated that line myself for a permanent fix... :)