"Dream Break Code" Reading Note III: summary of the book

Yesterday finally read the dream broken code, time is very fast, read very urgent, many places without careful scrutiny and thinking. But still can understand the main meaning of the book, or have their own experience and feelings.

As the author put it, "This is a story about a team of men holding up a code boulder, trying to push it to the top of the mountain, though suffering, but still struggling to create something useful, rich and enduring," and perhaps the biggest gain is a deeper understanding of soft engineering.

We find the software difficult to deal with because it is invisible, invisible and not the only problem, and we cannot see power, magnetism, or gravity, but we can reliably predict its behavior for most practical purposes, but we have no theory that can be used to calculate limitations on software size, performance, and complexity. It's not even logical to explain what a software product does and how it does it. As the joke about software engineering says, if you can't reproduce the problem, programmers won't be able to solve the problem.

We find the software difficult to deal with because of the following points:

1, the computer strict logic and accuracy, with the human not strict logical, vague and changeable mode of thinking between the contradictions, resulting in the communication between the human and machine barriers.
2. The cost of communication and collaboration between the development teams leads to the addition of manpower to the projects that have been delayed, only to keep them from being delayed.
3, the project objectives are not clear, target change to change, so sometimes decide what to say, more difficult than how to say.
4, the project goal is impractical, from the beginning to want to do a suitable for all, can do all things system, resulting in the same as the eternal motive of the outcome.

Even if we face the ordeal of software development, we also follow the principle that we consider the software to be well designed: strong--good structure, no defect, applicable--"the program should conform to its set goals"; pleasure--"the experience of the journey should be pleasant". In the beauty of programming, there is a saying: "Programmers are said to have a dream to change the world: programming magic and full of power, countless young people join in, with dreams and thinking to change the world." "For us to have such a dream and to realize the joy and satisfaction in the realization of the dream, then no matter what the outcome, it should be a very happy thing."

Due to the rigid requirements of the job, it is not free to choose the progress of reading. "Dream Broken Code" although read, but I think also will be in time to take out again, after all, knowledge is restudying. Do you have a light on the deadline you're going to read? , will try to ensure the quality of reading and blog quality, under the premise of appropriate speed up the progress of reading.

"Dream Break Code" Reading Note III: summary of the book