"Dreaming in Code" has finished the last chapter of "large cattle" mentioned in the article of "deeds" emotionally.
Before read this article, feel that foreign IT sector of beach-goers, after reading the article, not only sigh, although they realize a lot of well-known project, did a lot of good software, but to be honest, they (the book the characters) project management capabilities and the ability to develop software is really limited. They always entertained ambitious goals, the grand ambition to do Chandler, they always want to give users the best experience, use the latest technology, hoping platform, hoping to open source, but there is no clear time limit, they did not know to their own lack of ability, but feel that they really can change the world, it is this lack of understanding of their own, the lack of knowledge on demand, lack of knowledge of reality, that makes this huge investment, consumption of the giant long " great "project to nothing.
In the whole process of software development projects, like countless failures, such a huge failure can always remind me, and made me think about the software development process, thinking, before actually to implement software development, not only only need to develop a detailed development plan, but also a clear understanding of their own strengths and weaknesses, clearly developed a set period of time and the duration of the development goals.
Mentioned in the text, software design has two meanings, one is we want to build the product, and the second is to allow products to be implemented in software engineering, I believe there are two different roles - subject matter experts and engineers. Only know how to code a programmer can not always become experts and engineers. Although the code is the basis for software development, but only a part of the code software development do not represent all the core software development is not a code, but the software design process, the management process. Software development process like a levy, a module of any instability will have an impact on other modules, and even cause the entire building to collapse. Whether in coding or design process, we always adopt the idea of divide and conquer, divide this processing module and ideas is a task decomposition in accordance with waterfall, in the code not only to consider the coupling of the code, you should also look at the interaction between the different modules. Software development life cycle is essential to consider the situation in the development process, whether there will be lack of execution, the length of the code will affect the design cycle deviation needs and so on. Like Chandler developers and decision-makers, their life cycle and no real knowledge and understanding, and ultimately lead to the failure of the project.
And all occupations, always adhere to the programmer's point is rigorous, we must clearly recognize that God is not a programmer, any piece of good code is not written once, it is always through continuous attempts, continuous improvement, constantly temper.
In my own software development process, often there will be big changes in the development of the middle or even the way new ideas need to add functions appears, after reading this book, I reached a daily epidemic registration system to re-do the head of the APP a detailed plan, in addition to the already completed section also contains functional design, planning and development cycles, daily schedule planning section is not completed, all of the features and schedule planning are based on their ability to learn and the knowledge currently available. After these detailed planning, the first time that the idea of software development process is so clear, but today the implementation of the task, leaving the passion I have developed really see the progress of the development progress.
When I see the interface smoothly conducted today, when the function has been achieved, seems to have a deeper understanding of the word engineering software engineering. I believe that the essence with the continuous learning and growth, and I can be more in-depth understanding of software engineering. Also thanks to "Dreaming in Code," this book gives me the software development process inspiration.