I feel like I make such a mistake all the time, I want to understand everything I do, and I have to do everything to be perfect and the best, but I fall into the abyss of details. However, in the end, there was no overall grasp, and the things that were made either dragged on for a long time or could not be made at all. This feeling should be the technical cleanliness of programmers who have read an article before. Ignoring the actual situation, I want to wait for all the conditions to be mature and all the technologies to be understood before starting and doing one thing. . In the end, nothing can be done.
Because it is almost impossible to understand everything, and there is new knowledge every day. There is no need to spend a lot of time to learn a lot of things. You can find an expert in this field, simply train you below, and you can carry out the work, or you can ask an expert in this field to complete it, saving trouble and effort.
It is almost impossible to start when all the conditions are ripe. When a project starts, all the modules are just starting, and they are not stable. You can't wait until everyone else has done it before starting. You can completely stub the modules you depend on and continue your work.
The progress of any project goes through many iterations before there is a finished product. All if you don't focus on the main problem at the beginning, and blindly engage in some corners, the results will definitely not be good. For example, if you do a project, it is a technical project, that is, a prototype. In many cases, there is no need to pursue perfection. It is enough to make the prototype run and complete the corresponding functional verification. As for performance and stability, it's all to consider when making a product.
Just like building a house, the first thing to consider is the foundation of the house and the position of the main pillars. Don't think about how to put a brick here.