When a framework embraces conventions, developers familiar with the framework can move from project to project with minimal "ramp up" time in order to become familiar with each project. Now before you think it's all fun and games, here are some points to consider as you embark on your journey building large apps with Angular: Convention vs Configuration Directives became my best friends, Angular best practices got me up and running, and I began derive real satisfaction from my work. After a few months of hate/love, things started to click. to understand my new book "Directives for Dummies". Then my new race car broke after 10 loops around the track, I found that none of my previous toys played nice with my new ones, and I realized I would need a Ph.D. My first few weeks with AngularJS I was like a kid on Christmas morning, unwrapping presents as fast as I could and running around showing everybody. To misquote "I'm Sick of the Web: 's Healing Balm". Not with NodeJs, not with NoSQL, not with BackboneJS. Work with a RESTful interface (for real)Īngular is not the framework to end all frameworks, however, never before have I derived so much pleasure from web development.Does that sound like a dream come true or are you still wary? Either way, you will inevitably run into a problem that Angular does not solve for you. Whatever your experience with Angular and whatever size of project you're working on, there will come a day when you encounter Angular in the wild being used on a large project. New to AngularJS? Confused by directive mumbo-jumbo? Giddy over Angular's magic and your new productivity? Jaded by gotchas you didn't see coming? Enjoying the zen of Angular?Ĭheck out my presentation on building large apps with AngularJS
0 kommentar(er)
