[Eng Sub]if (extensible design) return "work life balance"
summary
Claims a layered front-end redesign that separates UI, feature wiring and business rules into action layer, service layer and reusable UI atoms, uses Storybook, HOCs and a config + feature flag admin to drive module behavior, and runs in a monorepo. Built modules let one codebase serve multiple product versions; swapping a layout now takes under a day, duplicate coupon/login logic disappears, and UI and script teams ship faster with fewer human errors.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:53Extensible design needed
- 1:59Original structure problems
- 3:45New design goals
- 4:31Atomic UI design
- 5:56Separate UI and logic
- 7:02Feature and action layers
- 8:27Service layer creation
- 9:55Layer interactions
- 11:01Duplicate code resolved
- 11:25Multiple service versions
- 12:32Modular product configs
- 13:42Feature flags control
- 14:45Dynamic config tool
- 15:51Monorepo structure
- 16:35Work-life balance gains
- 17:39Team feedback benefits
- 18:43Key takeaway
- 19:30Final thoughts
related talks
37mPragmatic crafting
21mShared Components Beyond the Design System
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
27mMicro Frontends: Break Up You Web App!
37mDemystifying Micro-Frontends
29mMicro Frontends, or How to Evolve to an Extensible Frontend
22mBreak Up With Your Frontend Monolith
39mTomorrow's UI Architecture — Structuring UI applications Around Features