There is a long going discussion on fat-this and skinny-that when building software systems. Obviously, you want to avoid fat classes all over, but where do you put the code then? In this two-part blog post, we explore the layers provided by Rails and look out for new places to divide our code further.