Backend lego

I think I've finally found a way to get a more intuitive understanding of the MVC approach to programming. It seems the words model,view,controller doesn't really mean that much to my brain, and I always have to think twice about which is which and which does what. So, after some thought, here is my nomenclature solution to the problem:
Model = backend lego
View = frontend lego
Controller = engine / in-between-code / translator

In other words, a backend is built from backend lego, a frontend is built from frontend lego, and then you have some interim code inbetween.

I find this much more intuitive than remembering that modelling is something not having to do with views, and trying to fit a controller in there somewhere.