MVC: The Most Vexing Conundrum
Elementary explanation of the Model/View/Controller design pattern, particularly as it applies to Ruby on Rails. Extremely concise explanation that should be everyone’s first stop in understanding Rails (or any other MVC based framework). I wish I had found this a month ago.
Anyone who writes any Rails code should have a solid understanding of MVC, since it is the basis of just about everything you do in rails. To provide a bit of a preview to what you find in the article, MVC, which stands for ‘Model-View-Controller’ is a design pattern commonly used by Web apps. A Design pattern is an architecture for writing software. Common design patterns such as MVC have evolved over time as developers find better ways of doing things.
The MVC essentially advocates dividing your program into three somewhat seperate parts. The Model, which handles your data records, the Controller, which handles what operations can be performed on the data, and the View, which governs how the results of Controller operations are displayed.
If you are new to Ruby on Rails, or haven’t heard of the MVC pattern before, I would really recommend you read the article!
[…] First, before you read this article, I would suggest you read my first post on the subject, and this article. […]