Topic
5 articles found
If you are a Software Developer of some form or another, chances are that you follow what are considered best practices for "Clean Code"or "Clean Architecture". It's considered generally best practice according to these books to keep functions down to a few lines, ensure classes have exactly one rea
Why architecture matters in a research project Most research prototypes are throwaway code. NumPath is not. It needs to survive four phases over 30 weeks, accumulate real student data for a randomised controlled trial, and remain testable without live infrastructure at every step. That means the arc
An architectural doctrine for NestJS projects: a breakdown of typical codebase degradation scenarios and the structural constraints that keep them from emerging as the feature set grows. This article is a breakdown of how a typical NestJS backend degrades as the feature set grows, and how the ideas
Every React Native codebase I've worked on hits the same wall around month four. A screen that started at 80 lines is now 400. Half of it is useEffect chains coordinating API calls. A push notification mid-flow leaves the app in a state nobody can reproduce. Clean architecture in React Native isn't
For decades, we repeated a simple idea: code is read more than it is written. So we optimized for readability. For naming. For clarity. For structure that could be navigated by someone who didn’t write the code. That assumption is breaking. Code is now generated more than it is written. It is traver
