Abstractions in Angular
summary
Angular traces how controllers and directives give way to components and services and how adopting TypeScript interfaces forces concrete business models. An example fence-order app maps customer, order, product to UI pieces like order form and product card, shows which abstractions become components versus services, and uses data binding and templates to connect them. The claim is that this mapping uncovers missing requirements, improves stakeholder communication, and yields a working single-page implementation that clarifies the domain.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:20Fence
- 2:06Key Abstractions
- 2:24Page Abstractions
- 2:51Software Abstractions
- 3:13Angularjs Abstractions
- 4:00Angular Abstractions
- 4:57Developing the Business
- 5:52Learning about the Business
- 6:36Outro
related talks
27mAngular Architecture: From Patterns to Implementation
28mReal-life Angular Architecture Lessons
18mFlexible data flow architecture in Angular
27mThe good, the bad and the ugly - Component architecture at scale
26mSoftware Patterns and Design with AngularJS
43mUsing Components in Angular 1.5
24mDay 2 Keynote, Angular Architecture Concepts and Practices
28mFrom Scratch to Screen: The Art of Component Design in Angular