Chaos in starting a project?

As we all know, it is crucial to start any project with a good organization and structure, whether it is an individual or group project. First of all, we have to write our ideas on paper and pencil and always consider options for new functionalities, that is, we have to consider scalability from the beginning.

Let's consider a classic example of a project, a web development, to carry it out there are a lot of tools and software, so it's crucial to choose the environment well so when we reach the first case of success, we have support and a development community.

It is important to clarify the innumerable variables that must be considered when starting a project, one of them is profitability, and considering if it has a target market, given a positive case in their study, it is essential to have a minimum viable product, for our example of a web project it would be to do it with the most complete and innovative software available, adapting a very effective architecture, being able to be a monolith, this means, where the frontend and backend are not separated but interact with each other.

After this, when it is considered a successful case, progressively improve the development to gradually add new functionalities, separating the application into micro services. It is opportune to clarify that there is no general formula for the cases of success in initial projects but with perseverance and providing the added value it can be made very profitable in the long term, so the chaos of the beginning of a project is normal.