Setting up Enterprise Frontend for Success
summary
Goal is frequent, daily releases of high‑quality frontends by combining specific practices: monorepo to avoid version drift for shared components, runtime feature flags to decouple deploy from feature enablement and roll back without redeploy, and trunk-based development with short PRs to eliminate long‑living branches. Enforce strict TypeScript, Prettier and ESLint rules, require short design docs and weekly design reviews, and measure success by faster merges, fewer rollbacks and delivering features to customers every day.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:58Enterprise frontend success goals
- 4:46Engineering ownership pillars
- 5:28Team communication best practices
- 6:32Monorepo and feature flags
- 8:45Runtime feature flags benefits
- 10:11Complexity vs complication
- 11:56Trunk-based development
- 13:19Code reviews and standards
- 15:03Code style enforcement tools
- 16:27Developer testing ownership
- 17:31Design documents and reviews
- 19:56Daily releases goal
- 20:40Summary of success pillars
- 21:00NgRx support and resources
related talks
22mSetting up Enterprise Frontend for Success
23mFront-End Platform Engineering
25mEnterprise Final Frontier – is it possible to change the corporate ways...
11mTransforming Enterprise Frontends with Micro-Frontend Architectures
44mBuilding resilient frontend architecture
15mEstablishing Platform Teams to Utilize the Economy of Scale
28mMind the gap: closing the rift between front and back
34mMass Frontend Refactors: Less Stress; More Success