The Road to KiwiEngine — Why I Stopped Thinking in Frameworks
Drew Marshall discusses his shift in thinking about software development, moving away from traditional frameworks towards a more modular and composable approach. He emphasizes the importance of designing systems based on contracts and predictable behavior rather than being locked into specific frameworks. This change in perspective has led to the development of KiwiEngine and the CitrusWorx ecosystem, which he plans to document publicly.
- ▪Marshall found that traditional frameworks led to chaotic and fragile systems.
- ▪He shifted his focus from frameworks to contracts and modular infrastructure.
- ▪Over 10 libraries related to his new philosophy have been made publicly available on NPM.
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 === 832808) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Drew Marshall Posted on May 27 The Road to KiwiEngine — Why I Stopped Thinking in Frameworks #buildinpublic #webdev #architecture #softwareengineering Over the last few years, I kept running into the same problem while building projects: Every tool solved its own problem well, but the overall system kept getting more chaotic. Frontend frameworks handled UI. Backend frameworks handled APIs. Cloud platforms handled deployment. CMS platforms handled content.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
