"Dream Break Code" read Note 01

"Dream Break Code" read Note 01

Reading the first three chapters of the Dream break code today, I feel as if the size of the modified form is flashing: scary. This feeling is a very ridiculous summary, but this is a programmer in practice really encountered the real experience of the problem. Yes, when we write programs, we often modify bugs much longer than we write code, and some of these seemingly small problems, we don't know how much time to complete the changes.

Chapter Two is an innovation, although the idea is very simple, a lot of people can think of, but in the end how many people can make it, and who can try to achieve it personally? This makes our development will lag for many years, this may also be restricting the development of software a small reason for it.

Lotus was a very good trigger for the innovation software, but it was not able to play the role that he could have been able to play because of the manager's reasons or the reasons for the time. A good idea can sometimes change an era, but sometimes an untimely thought will put his whole effort to naught. To adapt to the human adaptation of the machine this is completely inappropriate and appropriate, the machine is for human convenience, the development of fast key, should let the machine adapt to people tired. Software is the same, we do the software should be user-friendly, so that our users can be very good and convenient to use.

The program should be an optimist, because in the future will encounter a lot of difficulties, if not optimistic to face, then you will be down. However, we should not blindly believe that the future of forgetting the past, should be a good summary of reflection, with a more rigorous attitude and thinking about our work.

Chapter III

Friederico suggest: Be prepared to discard everything, because you probably can't do it all at once. Yes, the software must be based on the user or real needs to improve at any time. This reminds me of the teacher's agile development in class, first constructing a framework and then perfecting the software step-by-step, as required. This can be good enough to adapt to the customer, so that the software good development. Comparing software to an onion can be very appropriate for my current perception.

After reading these chapters, it is difficult and difficult to describe software engineering, even though it may not be outdated to read it in 5 years. 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.

"Dream Break Code" read Note 01