You know the old adage, how do you eat an elephant? One bite at a time. Well, I think this applies to software development as well. When developing a piece of software, it's important to have the overall picture, the elephant. Then describe what the software does, and what each piece is for, what the function is, what it will accomplish. Once you have the overall picture, it is then important to break down the project into accomplishable goals, or sections that can be developed, deployed, and then appended to.
I'm not talking about doing a sloppy job, and saying "we can fix it later." I'm talking about doing a good job, and building one part at a time in such a way that they can be plugged into the next part.
It is true that a software project will often have interdependencies between the models and functions. But if you are aware of the bigger picture, you can account for this. There are programming techniques to help along the way.
I just wanted to jot down these notes to help people realize that a software project doesn't need to be done in one large and long process. Rather, it can be accomplished in sections, and released in components as needed.
And to underscore all of this, it is important to utilize a framework that allows all this to be possible. This is why I have stuck with Django, because Django makes additions, subtractions, and alterations, relatively easy.
Til next time.