MVC: Model, View, Controller
When one function reads the library's data, applies its rules and draws the page, every new screen copies all three jobs and the copies drift apart; MVC splits them into a model (the data and the rules), views (how it's shown) and a controller (what a request does), so a new screen is a new view and a rule lives in one place.
Updated

- Category
- Data Structures
- Level
- Journeyman
- Tags
- Model-View-Controller, OOP, Separation of Concerns, software-development, Strategy Pattern