Reading "The path to mountains" and the harvest of modern software engineering handouts-Hong

About the path to mountain migration:

Before this assignment came down, I had already begun reading this book, so that the only thing I was lucky to see when I saw such a large volume of jobs was that there was a book in it, then I read 1/3. When I first read "The path to mountains", I was very slow, because I was not used to this style of style book for the first time, I don't know whether to watch novels or tool books. It was not found that this is not a tool book until we gradually saw it later. It is more of a guiding material, and it does not teach us how to use Visual Studio from the details, instead, it provides a macro guidance on how to complete various software engineering projects by using these software tools or independently or collaboratively. After grasping the context of this book, I gradually accelerated reading for two reasons:

1. Some large project team models do not have much reference for us now, and there are many things we don't know. For example, the waterfall model spiral model and other concepts, although literally understood at first glance, but it is not the same if they can be freely applied in real projects. For example, the release of software and the continuous update of multiple versions, many of which can only be simplified or even omitted at this stage, and the excessive pursuit of integrity is likely to lose sight of this. Therefore, the content in many books can be swept away and understood a little.

2. The idea in this book is the same as the idea that Mr. Yan Xin instilled in us. That is to say, we should first create personal projects, then cooperate with each other, and finally cooperate with the team. Therefore, when working on a personal project in the early stage, you do not have to forcibly understand the cooperation and teamwork between the two people. When working on the cooperation between the two people, you do not have to rush to see the cooperation of the team, it is also a step-by-step reading process.

Lecture on modern software engineering:

I was most impressed by the innovative misunderstandings that the teacher spent several classes talking about. Many examples are given in the handout, but I noticed that the interesting thing is: all these innovations do not point to the same conclusion. Some ideas that can be successful in this field may be severely damaged in another field, the best product is not necessarily the most successful development. I don't know if the teacher intends to cultivate such a thinking. However, my conclusion is: true and lasting success is not only created by the strength of a certain level. If we only focus on some aspects of research, maybe we can eventually become the authority in that field, but we need to become the leader and Vane of an industry like Apple's, apart from the technical factors, A series of factors, such as a long-sighted sense of smell, are indispensable. Of course, the latter is not necessarily better than the former, and each person has limited energy, so it is difficult to reach the peak in a certain aspect. This is just a different pursuit of everyone.

 

Some questions after reading:

1. whether it's the "mountain migration" or the course handouts, the overall starting point is relatively high. For us who have just begun to learn and adapt to this aspect, sometimes there is a feeling that the castle in the air is just as imaginary, I don't know where to start.

2. it may be that I am not used to foreign teaching models. There will always be an illusion that classroom handouts do not have much to do with what we are doing, but if you think about it, it is still related... This feeling is quite tangled...