Confusion calling model functions

[eluser]jedd[/eluser]
I have a comparably passionate hatred of the _model suffix on model names, too .. but on this one I am very much alone I gather.

In my current unlikely-to-ever-be-finished app, users of my site interact with the user stuff by hitting a controller called People, and the backend model that does most of the DB stuff relating to these tasks is called Member. There is not a 'user' in sight - even in my table and column names. (I'm quite happy about this, though I realise this is an uncommon reason for happiness.)

Similarly, my Forum and Mail controllers both talk mostly to my Message model.

I could go on ... and if you stick around these forums you'll see frequent proof of this.