I have been working on a small project over the past few days.CodeThe scale is small, but I suddenly find a problem that I have never considered before. do such a small project need to be analyzed and structured.
In fact, every one of us will conduct problem definition, requirement analysis, software architecture, software construction, system testing, etc. during project development...
Just as the project grows, these jobs become more formal. cainiao, like me, develops small projects. At the same time, these preliminary jobs are subconsciously carried out in their minds.
But today I encountered some logic troubles when I was working on the project, and it was difficult to think clearly about it. it took me one day to fix the bug. I suddenly thought that it would take much less time to complete the preliminary work than to correct errors. this should also be advocated by all software engineering-related tutorials, although I am not very familiar with it. but if you want to read a book, you can just drop it. therefore, I think we should at least do our preliminary work well in small projects. We don't have to be more formal, but we must make ourselves clearer about the projects you have developed. of course, For details, refer to relevant books. but we should develop such a good habit.