Legacy's End: An RPG Adventure Toward Clean Architecture
summary
An engaging talk that frames moving toward clean architecture as an RPG-style journey with levels and enemies, aiming to stop frontends from becoming painful to maintain. It explains how concrete technologies and patterns—Shadow DOM, inversion of control (IoC), the dependency inversion principle (DIP), Context API, and isolated testing—help produce cleaner, decoupled, and more sustainable applications.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:12What is Legacy's End
- 2:58Demo with browser AI
- 5:12CSS global issues
- 5:57Web Components and Shadow DOM
- 7:46Monolithic code handling
- 11:21First mission complete
- 11:43Dependency injection
- 14:37Contracts and TDD
- 23:06Constructorless injection
- 24:35DI testing
- 26:43API adaptation
- 28:52Final mission and conclusions
- 30:18AI best practices
- 32:05Q&A
related talks
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
41mUsing Boundary-Driven Development to beat code complexity
47mA Crusade Against Legacy in Frontend Projects
48mLegacy, for lack of a better word, is good
44mBuilding resilient frontend architecture
01h 01mClean Architecture
47mStep by Step Toward Clean Architecture
55mClean architecture that harms your code