Dream Break code--end

"Dream Break Code" this book read for nearly one months, and finally finished reading, although not carefully read, but still understand its general content, know what to say. Originally planned every three chapters to send a reading notes, because the time is very tight, did not follow the plan, I usually look at night, after reading the late hair, has been dragged to all read.

The book's translation refers to the outcome of the Chandler project, which has failed and has become one of many failed software projects. This ending undoubtedly added to the weight of his heart after reading the book: software is really not easy.

Today's software projects, has become a complex construction, the changing application environment (including users), so that the software needs are constantly updated, today 100 requirements, tomorrow minus 10, 5, plus 80, This is evident in the ever-public release of the updated open source software and Web site applications. In order to meet this demand and the cost of programming and debugging resulting from this demand, many methods have been invented, such as once the project is considered "large enough", to use object-oriented instead of process-oriented, and the use of object-oriented component-oriented-----But all of these, in the face of complex external requirements, Programmers feel that it is still far from enough.

I'd like to think more about the optimism that over the years, the accumulated approach has actually greatly improved the programmer's ability to solve problems, and the libraries and frameworks are getting bigger and they are really reducing their problems. The terms "practical minimization" do not conflict with the "methodology", they are always in relative change, that is to say, with the continuous improvement of methodology, the threshold of "practical minimization" is actually increasing: Today a feature that is considered tricky by 3 programmers, Perhaps 2 years later, a single program can be easily completed on a single frame.

The difficult and difficult description of software engineering in "Dream Break Code" may not be outdated even after 5 years of reading. Because, as the original author said, the book depicts a team of people shoulder the code boulder, although the ordeal still want to push it to the top of the story, and it is this story of the world today millions of servers and PC running on the various software, the achievements of mankind constantly beyond the realization of a greater dream.

As a computer professional students, I know that I am not as good as those programmers, face c,c++,java those languages, each one is very confusing, I have not been introduced to the present, I think all is very sad, even so, I do not want to give up, I do not know what I really like, I can only in the programming this road struggle, Maybe one day I can find the fun, overcome the difficulties, but also can be tortured no more to engage in software, no matter how, or to try to give yourself a chance.

Dream Break code--end