Claprec: Engineering Tradeoffs - Limited time vs. Perfection (6/6)
The article reflects on the development journey of Claprec, highlighting the tradeoffs between limited time and achieving perfection. It discusses the challenges faced during the project, including architectural constraints and the decision to prioritize functionality over ideal performance. Ultimately, the author emphasizes the importance of delivering a working product despite its imperfections.
- ▪Claprec was developed over a year and a half, culminating in a functional application.
- ▪The project adhered to N-Tier Architecture due to university requirements, which posed both challenges and advantages.
- ▪The application currently lacks a caching layer, impacting its performance, and immediate improvements are planned.
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 === 442269) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Kenan Sejmenović Posted on May 22 Claprec: Engineering Tradeoffs - Limited time vs. Perfection (6/6) #softwareengineering #techdebt #lessonslearned #experience Series Roadmap Product Overview (1/6) Architecture: N-Tier Design, Decoupling, and Microservices (2/6) Frontend: Angular, NgRx, and OpenAPI Integration (3/6) Machine Learning in Practice (4/6) Database Design and Data Modeling (5/6) Engineering Tradeoffs: Limited Time vs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
