The controller just is the glue to tell everything that needs to happen whenever you interact with it. so whenever you change the name, we clear out and store that name for later in the program whenever you start the game we tell the view to show the board ask the model to start the game, whatever that means whatever it has to do for the setup we update the players names get them off the model and pull them into the view we pull off the model where their positions are and then store them on the view so it also simplifies looking at your code cause you're not, you're not doing a whole bunch of fancy logistical code to it. it can make it a lot simpler now for a lot of people you realize this is gonna mean you're going to be a lot more code because of it but in the end the use benefit of it vastly outweighs the additional code that you're putting in. because if you take a normal game where you've got all the code strung together and try and move it to a mobile device, move it to a different platform or have to make a change you're gonna be going through a lot more code to make sure everythings glued together make sure you aren't missing a connection whereas with the control view model you're gonna know that connection and only have to make it in certain pieces of it but uhm, so ah what I see that we had a lot of hands on people that have used model view control, what kind of things have you guys used model view control for? &amp;lt;audience comment&amp;gt; &amp;lt;laughter&amp;gt; 