How we did everything wrong and got away with it (Angular success story)
summary
Converts a legacy jQuery front end of about 200 screens to Angular over three years, replacing a proprietary framework with reactive forms, onPush change detection, AG Grid, Mongoose for model validation, server‑side caching and a “poor man’s GraphQL” payload minimizer; fixes include switching template/reactive forms to reactive, addressing AOT quirks (private→public fields, unused HTTP imports) and dropping a broken draggable lib — result: large tables (≈4,000 items) load under two seconds.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:36About me
- 2:03About YOU Angular knowledge?
- 4:01Problem background
- 5:58Upgrade strategy
- 7:11Started with early beta version
- 13:26It is all JavaScript
- 13:52what could possibly go wrong
- 14:32Solution: Mongoose
- 14:57Regular Angular upgrades simple, just update package.json...
- 23:42Things I would do differently
- 24:49General room for improvement
- 26:47Closing thoughts
related talks
19mIn the Ocean of Angular Web Applications
22mHow to make robust and scalable front-end using layers
33mRefactoring 80+ Angular projects and what went wrong
20mBuilding Platforms with Angular
38mIntroduction to AngularJS
05mMigrating a Portfolio of Front-End Apps to Angular
43mSupporting an Old-Fashioned AngularJS App in a Modern TypeScript World
28mAccelerating Angular