Unleash The Power Of Angular With Knowledge of Patterns
summary
Argues concrete claims: dependency injection solves instance-creation pain, not just jargon; webpack/ES2015 still emit IIFEs so module behavior matters; Angular modules make providers global while declarations stay local (module providers global vs declarations local), causing shared-module and lazy-load gotchas. Demonstrates perf and correctness fixes: change detection demands new object/array references so use immutability rather than mutating in-place, avoid service-side race conditions by not storing ephemeral lists on shared services, and prefer small pure functions and strategy chaining for clarity.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:27Dependency Injection
- 3:56Explaining Patterns
- 4:56Is Dependency Injection overkill
- 6:34Common Sense
- 6:56Restaurant Example
- 7:51Module Pattern
- 8:20Module History
- 10:13Module Patterns
- 11:31Funny Picture
- 11:45Energy Module
- 12:19Function Declaration
- 12:41Model Declaration
- 14:00Common Problems
- 17:49Common Question
- 19:55Application State
- 22:45Immutability
- 26:50Summary
related talks
44mRockin’ in the Angular World
57mAngular Dependency Injection, In Depth
41mThe most infamous code smells in Angular Applications
18mLightweight Architectures with Angular's Latest Innovations
26mSoftware Patterns and Design with AngularJS
20mEngineering Scalable Angular Components
27mAngular Architecture: From Patterns to Implementation
19mTuning Your Angular Application