The book of the Law of construction

The Book of the Law of construction

I used to think that writing software was about 18 hours a day trying to beat the code before I learned software engineering. But after learning software engineering, gradually understand the far real software development, coding is only a small part. But since most of the books on software engineering are written in writing, it feels like a nut and hard to digest. After I learned the software engineering, I still feel mengmengdongdong.

But fortunately in the teacher's recommendation to know the "construction of the law." But at first I was full of fear, and I didn't turn it over. Later, the teacher mentioned several times, I finally opened the book, and then a brief encounter, a sense of welled up and come. This book comes from the requirement analysis of software development to the release of each stage, which also comes with some basic qualities of the programmer's requirements, such as code specification requirements, user experience, innovation awareness, professional ethics.

Where code specification I was deeply affected. Because in the current situation, I am often a person to write code, so the code is written in a brain, often without comments and some specifications, because the code I see. Later I learned that, to the future of software development, a person is difficult to complete, so often need to cooperate with others, then the annotations and specifications are very important.

Pair programming I've never heard of it before. Later, I saw that pairing programming was developed by a bunch of programmers, shoulder-by-side, equally, and in complementary terms. And from the reality of the driving plane This example to illustrate, very image, let me understand the software development there is still this existence, there is a chance I really have to try.

I've heard a teacher say that boys don't pay much attention to the user experience. It's not. I was also one of the previous, I often focus on the realization of the function, always feel that the more the better. But later through the book learned that the user experience of the software is extremely important. A good user experience will leave a good first impression on the user, is the foundation of software development.

Since I've seen "from 0 to 1", it's just that the book has something to do with it, so I've also looked at it a bit. Through several vivid examples of innovation, the book says that innovation is the source of software survival. Make us realize the importance of innovation.

But I also have some sections that I don't quite understand.

1, the sixth chapter, the agile development and rapid prototyping model is one thing?

2, the seventh chapter, this Microsoft Solution framework I see a bit not quite understand. What is he probably talking about?

Overall, Xin Zou Teacher's "Construction law" is a grounding gas software engineering books, not genteel text, easy to understand. But after reading I also feel that the knowledge content of the book involves a very wide, speak very full, but still need to practice more to receive for their own use, otherwise easy to forget.

The book of the Law of construction