[mdparker89]

I've seen this in iOS code. I think it's partly because MVC gets pushed so hard. For a new programmer, it seems as if the code has to fall in to one of those three buckets. Views and view controllers change pretty frequently so there's only one place left.

[zem]

yep, that was a large problem in the early days of rails too, where everything got pushed into the model simply because it was neither a view nor a controller.

[donw]

Exactly. A lot of people learn to code for practical reasons -- which is great -- and cut their teeth on a Rails or iOS app, where there are a set number of "buckets" for where code goes.

The idea of just creating other objects out of rainbow tears and unicorn dust doesn't naturally flow from this style of learning to program. :)

[girvo]

Amen. PHP had the same problem, and in some cases still does, but thankfully I'm seeing more and more developers (and more and more projects I'm working on here at work) where it's all Plain Old (language) Objects with some nice sprinklings of proper libraries to get stuff done. What's lovely about that is everything ends up being completely unit-testable without much extra effort. It also means I get to use proper OOP architecture yay!