By reading this book, I am very glad that they can form their own good programming practice at the time not yet read this book, but also a new understanding of the future of software engineering development, I used the naming of variables is random, that is, Pinyin, because English is not very good so we just played, but now I know this is a serious flaw.
This book is interesting, very attractive to me, the book simple image illustrates some basic problems of software engineering industry, and some of the mistakes we make as a beginner tends to influence the development of the program in late, wake us from outset the importance of code written specification.
"Building of the law" in the beginning of the course gave us a detailed lesson plans, and educational purposes, objectives and means. As well as the classroom teacher talked about, like, let ourselves think about what is the real health of the teacher-student relationship. Then the book in plain language about the concept of software engineering, and other disciplines analogy outlined our development prospects.
By textbooks and classroom, I understand software program = + software engineering .
Program (including algorithms, data structures) are basic skills, but above algorithms and data structures, software engineering determines the quality of the software; business model determines the success or failure of a software company.
The book team were from individuals, both in terms of software development to the people after the stage, and mentioned some of our own mistakes, no major problems in their own time alone, but when combined together, that is, very serious mistake. Thus I think it is a software engineering overall, because the project is hardly a person's job, and often in collaboration with relevant and significant association between early and late, we should learn to write the habit of some standardized road, though many are in after the job will be some opportunities, we should also reflect on their own in time, we must recognize the impact of his momentary caprice or convenience versus team caused, so as not to cause delay or function works together with less than caused implementation flaws.