I'm learning how to program and study dozens of things at once because programming is my job.
What I would like to know is about MVC.
I figured that in relation to MVC, the view V should have its HTML ready right at the start of the project, which would allow a better understanding of what is being done.
>Is my conclusion correct and having the layout ready facilitates development with MVC?
I think so. The idea behind MVC is to separate the responsibilities of the various components and even the tasks to be executed in the project.
But if you consider that the layout is never ready, it does not make that much difference. Each one can find its best project management model. This may vary with the number and specific qualification of your members.
Some may say that all backend and controller ) should be done before and with the proper specification of this responsible for mounting HTML should build the layout as you like. Others will want to build HTML and then start specifying what the controller should do, and define what the model should look like. Both approaches can produce better and more productive results under different circumstances.
Try both and see which is best for you. When you have experience, you will know how to choose beforehand in each case. Obviously a hybrid solution is possible.
What is certain is that you need the requirements first. Even if obtained informally. It just can not be in the achometer . Amazingly, a lot of software is done without it. It can be dangerous to do the layout to find the specification. But there are cases that, done with care, may be a valid option.
