> [!tldr] A good principle for writing code When it comes to writing code, especially on large code-bases, a good principle to aim for is to *maintain separation of concerns*. **Each thing should have one, fairly self-contained purpose.** There should not be implicit dependencies, or explicit-but-surprising dependencies between disparate chunks of code. Separation of concerns is a key factor in delivering [[Highly Cohesive, Loosely Coupled]] code (or systems design). **** # More ## Source ## Related - [[Highly Cohesive, Loosely Coupled]] - [[MVC Pattern]]