Evolutionary UI
summary
Applies evolutionary architecture principles to UI by making fitness functions the control mechanism: concrete examples include running Google Lighthouse for accessibility and a performance budget (NPM tools mentioned), enforcing a lint rule on GitHub to disallow shallow rendering, and measuring cycle time with a 30‑minute threshold. Advocates micro-frontends for independent deploys, recommends subcutaneous (quantum‑level) tests instead of brittle shallow unit tests, and discusses tradeoffs when constraints collide (bundle size vs heterogeneous frameworks).
AI-written summary · about
chapters (7)
- 0:00Start
- 6:40FITNESS FUNCTIONS
- 22:42THE TEST PYRAMID
- 25:45TESTING: FLEXIBILITY
- 28:58SUBCUTANEOUS TESTING
- 32:21PARTITIONING COMPLEXITY
- 35:07Potential Solution MICROFRONTENDS
related talks
01h 03mEvolutionary Software Architectures
53mEvolutionary Architecture: Principles and Patterns
42mBuilding Evolutionary Architectures: Principles and Practices
43mEvolution of Functional UI Paradigms
52mBetting on Evolutionary Architecture
41mOrganising and Governing Evolutionary Architectures (Fitness Functions)
50mTowards an Evolutionary Architecture
40mPractices from trenches for embracing evolutionary architecture in wild
