skinny controller or skinny model?

[eluser]cartalot[/eluser]
My newbie perspective

start with a fat controller, and then as you test and develop -- push functions and code to the model when you know they are working --
to then make the controller skinnier and more elegant.

that way the controller is your main development area/ sandbox -- you arent trying to debug code in both the model and controller. and then the more code you push to the model, the easier it is is to see the overall logic going on in the controller.

another suggestion is to standardize the sections of your model, and try to follow or label them the same way.
like validation, insert, update, delete etc.