"Dream Break Code" Reading notes of the No. 0 and 1th chapters

At first, the view of software engineering is to face the needs of customers, to write a lot of different small programs to build a customer satisfaction with the software, it is so simple. I've never seen a book.
In the software development of the book, there is no real development of a software, so I do not know the real process of software development, but the book's recommended preface CSDN President Jiang Tao words caused me to read this book
Interest, he said: "The Dream Break Code" shows us how Silicon Valley's first-class software developers are doing product development ... "
The author from the No. 0 chapter, is also in line with the quality of the people as a computer industry, we clearly know that the computer in addition to "1" is "0".
The No. 0 chapter, software time. For a while, the author was immersed in the day-to-day work of writing code, forgetting the time when writing code, or even waiting for the next colleague to come to work
I realized that I didn't go back all night. Such a spirit is truly unparalleled. But it also made me realize the hard development process of soft armor. Kung Fu is not a conscientious, I think as long as the efforts, the final success
is not surprising. The book said: "The dream of the Mail, the line of the----the Gates of hell," but I just insist, there will always be a day to climb out of hell.
The 1th chapter, the death is decided. The time it takes to develop the software seems really unpredictable, and the team in the story takes a lot of steps to improve the speed of software development, as much as possible to
Time frame, but many methods fail, and there are many reasons for failure.
For example, the story of system architect John Anderson said: "A lot of reasons." Before construction, there is a blueprint. We never had a blueprint, so we met unexpected problems. Unless you actually
It's hard to say how long it will take to make something. ”
Another example is the team's lack of teamwork awareness, the book Programmer Jede Burgiss said: "There are too many uncertainties, the time you need depends on other people's time." ”
There are also error estimates of the time it takes to fix a bug, which is more difficult to fix than Mulberry becomes satin, and that the time is far more than expected and eventually a "stall" occurs.
If existing programmers are limited in their ability to work, then it's good to add new people to the project, but then there's the Bruce rule: "Adding manpower to a project that has been delayed will only make it
Continued delays. ”
Does the free sharing of the source code allow the project to proceed faster? Compared to Microsoft's closed source code, I personally do not like it too much.

"Dream Break Code" read the No. 0 and 1th chapters of the notes