Setting up Enterprise Frontend for Success
summary
Practical setup: adopt an NX monorepo to share components and cache builds, use runtime feature flags like split IO and launch Darkly or Firebase remote config to decouple deploys from rollout, practice trunk‑based development with short PRs, enforce style and automation (prettier, ESLint, strict TypeScript), require developer-owned unit/integration/visual tests and design docs, and aim for daily releases so fixes reach users faster, rollbacks become rare, and teams scale without branching chaos.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:54Frontend success objectives
- 3:56Engineering ownership
- 5:02Team communication
- 8:11Feature flags and trunk-based dev
- 10:41Complexity vs complicated systems
- 13:11Code style guides
- 16:21Testing responsibility
- 17:49Design reviews
- 19:37Daily releases
- 20:42Implementing three pillars
- 21:02Enterprise support
related talks
22mSetting up Enterprise Frontend for Success
23mFront-End Platform Engineering
44m5 Building Blocks for Successful Frontend Platform
28mMind the gap: closing the rift between front and back
24mMicrofrontends
49mScalable Best Practices for Your Development Team
24mScaling Frontend Development using Micro-frontends
24mManage Your Huge Codebase like a Boss