#Skinny Everything (1 of 3)
At Revelry, we build web apps using Rails. Working with Rails, or any MVC/MVP framework for that matter, you always come across the saying “Fat model, Skinny Controller.” The idea is to slim the the controller down to basic CRUD actions, and put the rest of the more complex functionality in the model. It definitely is good to have a slim controller for sake of code reusability, readability, and testing. However, it is also good to have a skinny model. For the exact same reasons. In fact its good to have a skinny everything.
What tends to happen when you move all logic into models is that you get “God like Models” which become impossible to understand and maintain http://stackoverflow.com/questions/14044681/fat-models-and-skinny-controllers-sounds-like-creating-god-models. Jon Cairns wrote a great article about why “Fat model, Skinny Controller is a load of rubbish” http://blog.joncairns.com/2013/04/fat-model-skinny-controller-is-a-load-of-rubbish/. Cairns says
“No class should b