I'm currently in a entrepreneur-level app development, and I know what shitty code looks like. And then I hear the news that we might go a little about TDD. Then I think it's screwed, how can you test this crappy thing? I see this thing, MVVM, then I think It might be a good time to throw out some weights for our CONTROLLER.
A fat controller brings us the Massive View Controller. Since the view & view controller is so close, why can't we just let them be together.
Here's our problem.
Our controller contains too much logic, and actually at the beginning, what i heard from the handsome Stanford old man is, the controller just take the model, and show the view. The thing is that Our model is always a JSON or something like, we don't actually simply take it and display it. We need to do a lot of crappy things on it, then have a Jelly, display the Jelly. And those logic of producing the Jelly can be away from our VC, therefore away from our view, therefore making it more testable.
I'm currently in a entrepreneur-level app development, and I know what shitty code looks like. And then I hear the news that we might go a little about TDD. Then I think it's screwed, how can you test this crappy thing? I see this thing, MVVM, then I think It might be a good time to throw out some weights for our CONTROLLER. A fat controller brings us the
Massive View Controller
. Since the view & view controller is so close, why can't we just let them be together. Here's our problem. Our controller contains too much logic, and actually at the beginning, what i heard from the handsome Stanford old man is, the controller just take the model, and show the view. The thing is that Our model is always a JSON or something like, we don't actually simply take it and display it. We need to do a lot of crappy things on it, then have aJelly
, display the Jelly. And those logic of producing theJelly
can be away from our VC, therefore away from our view, therefore making it more testable.