MVC: Why Everybody Should Code with Rails at Least Once
Comments(1)
First, before you read this article, I would suggest you read my first post on the subject, and this article.
So now you know what MVC is. You know why it is important when designing web apps, and why is is considered essential in Rails coding.
Rails disciplines you into using MVC. I have been programming with Rails for about 2 weeks. Through the process, and being forced into using MVC, I have also begun to think in MVC terms. In fact, the Model-View-Controller design pattern has become almost second nature to me. I can’t think of a clearer way to design a web application.
This is amazing to me, because I used to be, and in many ways still am, a sloppy programmer. I ran by the seat of my pants, without much over-arching architecture, and little true design. My code always worked, and well too, but was a nightmare of a tangle to read and maintain. I am amazed at the clarity and simplicity that is presented when using Ruby on Rails. I can actually make sensible UML diagrams of my work, without it looking like Medusa’s hair.
That is why I would push for every programmer to build at least one project in Ruby on Rails. Not only will you find that your coding time is cut down, due to the quick nature of Ruby on Rails, but you will also be forced into using good style. Well, maybe not, but you will be forced into using design patterns. That is a great advantage in the long run.
