3 main shortcomings of FSD after 3 years of use
summary
Talk examines three major shortcomings discovered in the FSD (Feature-Sliced Design) approach after three years of using it with React. Covers how the author adopted FSD, the specific pitfalls encountered in real projects, and concrete workarounds or changes applied that eventually moved the codebase away from pure FSD. Aimed at middle-to-senior frontend developers, focusing on practical problems and solutions when applying FSD with React.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:50What is FSD
- 7:07FSD principles
- 10:13Why I love FSD
- 12:43FSD in real project
- 15:34Unstable shared layer
- 18:43Shared layer unreliability
- 20:32Business model in entities
- 22:59Cross-imports issues
- 25:49High coupling
- 27:35FSD increases coupling
- 31:51Solutions to FSD problems
- 34:21Reducing coupling
- 37:103 main FSD problems
- 38:14Q&A
related talks
45mDigging Deeper into Feature-Sliced Design
30mFeature Driven Architecture
44mUsing Different Architectures Inside FSD
01h 15mState management of React apps with the Focal library
28mLessons in Managing Technical Debt
01mWhat Aurora Scharff Thinks of React
11mEvolving DBS Frontend
32mMiss the forest for the trees: How frontend developers fail to be engineers