The floor problem: why every admin product wastes 3 months on the same foundation
The article discusses the common issue in developing admin products, known as the 'floor problem,' where teams spend excessive time rebuilding foundational components. This repetitive process includes creating authentication systems, data tables, and routing setups, which are necessary but not part of the actual product. The author emphasizes the need for better approaches to avoid this inefficiency in software development.
- ▪Every admin product typically starts by rebuilding the same foundational components.
- ▪The process often takes teams three months before they can begin developing the actual product.
- ▪The floor problem reveals itself gradually, with the complexity of foundational work increasing over time.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3950320) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Coreola Posted on May 26 The floor problem: why every admin product wastes 3 months on the same foundation #react #webdev #architecture Every admin product starts by rebuilding the same eight things — auth, RBAC, tables, forms, theming, i18n, feature flags, routing. None of it is the product. Here's why this keeps happening, and what to do instead. Every internal tool, SaaS back office, and operational admin product begins life the same way. Someone opens an empty Vite project.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
