04.2.2 · Skill in Software architecture
Separation of concerns
Keeping different responsibilities in different places in the code.
Separating presentation, business logic and data access keeps each easier to change and test. Mixing them makes small changes risky. The principle applies at every scale, from a function to a whole system.
Resources
none yetResources for this topic are being researched. Every link is opened and checked before it is listed.
Tools
none yetTools for this topic are being researched.