"Road to Jane: software engineering practitioners," say the book is a method of talking about ideas, from which all aspects of different angles, detailed parsing the meaning of software engineering in all aspects of the role and value. This book language is approachable, multiple references to classical allusions in order to clear and understandable reason, as the first chapter references the Foolish Old Man story to illustrate the nature of programming and engineering. The book I was most benefit is that it is really the core of the idea of software engineering clearly explained, as the book says: "The project is actually very simple to do, but we think of him as complicated."
1. In the last year of study, my understanding of software engineering is limited to the software, or that I only come into contact with the program, thinking that programming that is the core and essence of the work of software engineering, can say that I almost completely ignored the project of the word, I have not seen in software engineering into the actual work, ignoring the actual situation of the company, after I read the book to understand their project is unknown.
2. After reading this book I gain much: In the first chapter, I understand the nature of programming is the choice, sequence, cycle, and programming closer to the physical work in practice, the structure of the program = algorithm + + method, programming is just a process. In the second chapter, the author cited "Shou Shu ice pick from the heap," the story I was impressed, I think people in the past method of the invention must be a gifted genius, the author tells me people are lazy method invention , everyone can create their own methods, which forced me to think. In the third chapter, I first come into contact with a qualified team should have what qualities, I have not had a detailed knowledge of the team had not thought about it, and learned in detail the role of project manager and only after the text has repeatedly emphasized the project value manager, so I was impressed on this post. In the fourth chapter, the author makes me understand the importance of communication, does the actual work, if customers and developers can not understand each other work will be difficult. In the fifth chapter, the author illustrates the ultimate goal of a truth programming is to solve the problem, the code just knock on the process to achieve the ultimate goal, in fact, this seemingly simple truth is often ignored by us, and we often for homework the purpose programming, programming is often forgotten by us. In Chapter 6, the author straight to the point: language is only a tool, and I think that the result is similar, in practice I found that the difference between various languages is not large, the core idea is almost exactly the same, so I'm well aware of the language in the project actually plays what role. In the seventh chapter, the author close to reality, about the reality of software engineering, but because I lack the expertise, understanding is not very high. In the eighth chapter, the author once again stressed the importance of thinking, technology will never be outdated ideas, tips and ideas must sometimes learn to temper all the time, software engineering is the need to think about.
3. Read through the book I lament all the time he had been lazy and ignorant to think about throughout this book is forcing me, if only read listened, left ear and out, and did not read it, like, thinking only to harvest value, software engineering is no different. On the one hand this book I learned a core idea of software engineering, on the other hand it is a good habit to learn the hard thinking, good thinking can only learn on the road farther and farther.