"Dream Break Code" read NOTE 1

At the beginning of this book, the author tells us about the story he encounters at work, the development of a project, the difference between the time originally set and the time it was finally completed. The originally specified goal is not the same as the final completion. Now I have not done the project, but by writing the program can be realized, every time to get the experiment (here is for the simple experiment), thought in a few hours can be done, may be used for more than 10 hours, the problem is constant, either the problem is too simple to consider, or forget the use of a function and so on, miserable.

The Chandler project struggled on the tortuous road.

The first few chapters have been about the development process of a project, the problems encountered by the project leader, the problems programmers encounter, the development process of each project. Very clear said: Reading is not very clear, can not tell where is where, do not know that is the project, that is the company's name. Don't understand what the author does with this? Is it a lesson for everyone? Or do you analyze the problem? But I've seen the developer's insistence on this article. Everyone encountered difficulties and did not give up, but to find the problem, to solve the problem. This is what you need to be aware of in the process of developing a project. Perseverance is victory.

"Dream Break Code" read NOTE 1