Dream Break Code Reading note Three (8 chapters-end)

"Dream Break Code" in reading and stopping, the time is fast and slow reading finished. In the end I could not help but think of the beginning of the book in the content of the words-"This is a story, is also about Baiqian, is to write a software, but also write Baiqian software, is to write a group of people, but also write millions people." Anyone with a bit of experience in the software field will be reading this book and must cover the volume and sigh: It's hard to do software. ”

Admittedly, I don't belong to "a technician with a little experience in software", but I also learned from the book that it's hard to do software. Here to write the feeling of the last few chapters.

The 8th chapter describes the concept of instant paste, is still in the long Chandler development process of a meeting, Doussotte put forward each person on the whiteboard affixed their own instant stickers, each sheet of paper represents the same amount of work, each of which represents a single developer one months or two months of working time. This is the task of thinning, write to remind yourself at all times, clear plans, can enable individuals to better complete their tasks. Then, in the 9th chapter, the author discusses the methods of software development, including the agile development we learned in class. But there seems to be no way to become a law, and as software technology develops, so does the way it changes. The chapter concludes with the article "It doesn't matter," and the author Kyle claims that software history is over, and that it can only be perfected with a heavyweight methodology. This is undoubtedly a short-sighted software development, the future of software will do a completely different work, there is a great possibility of disruptive progress.

The 10th chapter engineers and artists to discuss the art of software, we often see the arts activities and scientific work as irrelevant things, in fact, they are similar, inseparable. No artistic software works are not favored by users, the blunt code needs an artistic interface to make users feel comfortable. A software is a work of art, the integration of art, will enhance the quality of software. At the end of the book, I only talked about the Chandler to the "dog food" version, the version that the developers themselves used, and finally we didn't see the birth of the 1.0 version, not the final direction, but the difficulty of reading it. At the end of the paper, the author writes about the gambling about computer intelligence, which is also a prospect. At the same time still do not forget to remind the difficulty of making software-"the more you understand the software, the less you will do software."

This is the first time I have read this kind of book, can say has the Enlightenment significance. "Dream Break Code" to show me the real software development of the difficult, and I usually learn a very different, also make me a new understanding of software engineering. The road to software is difficult and long, we need to lay a good foundation, step by step climb.

Dream Break Code Reading note Three (8 chapters-end)