A collection of 12 posts
Solving deep technical problems is fun. But by taking a step back and examining how we got here can be just as fun and useful. We pride ourselves on our technical abilities. But an even more important skill we can have is not technical, it is a pragmatic skill: we can ask "why?". Why is
We spend more time reading our code than writing it. That's why it makes sense to write code that is easier to read. The good news is that there are a lot of really simple things that can make your code much more readable. This post describes simple techniques to make AngularJS controllers and s
I just published the first draft of my opinionated style guide for syntax, conventions, and structuring AngularJS applications [https://github.com/johnpapa/angularjs-styleguide]. You'll find many of these and more explained in deeper detail in my Pluralsight course AngularJS: Clean Code (coming
Angular. Breeze. JavaScript and HTML5. These buzzwords have been getting a lot of air play over the past year. There are plenty of examples to introduce you to these technologies but how do you apply these to larger apps at your workplace? This is where I find an end to end tutorial and demonstratio
Even if you've only read about Angular [http://angularjs.org], the odds are you've seen the rampant use of $scope in the C of MVC (controllers). $scope is the glue between the Controller and the View that helps with all of our data binding needs. Recently the Angular team opened up a new way
