"Dream Break Code" 1

"Dream Break Code" is by Rosenberg, a programmer with extensive experience in software development in the United States. This book is the author of the Osaf presided over the Chandler Project Field investigation, tracking years, trying to use the development process by Chandler revealed some fundamental problems in the software development process. It explores how to develop software through a story.

The author's idea of designing the structure of the book is amazing to me, there is the No. 0 chapter! In the subsequent reading process I was relieved, because the computer counted from zero. The authors suggest that in order to engage in software development, we must think in a computer-based way to prevent misunderstandings in the operation of the computer. Programmers should have this way of thinking, not only in life, but also in the application of theory to practice.

"The screen flashes when you change the size of a window in the Chandler software" The problem has plagued Anderson's development team, which has indefinitely extended project progress. As every programmer knows, it is very common that software projects are difficult to implement on a schedule. But what is it that has delayed the progress? Why increasing backup will only make it worse. I think, as Brooks puts it, "people and months are interchangeable only if the task can be assigned to many workers who do not communicate with each other." Whenever you join a new person, you have to let the old team stop working to explain the task, which is like a disastrous delay cycle that continues to extend. So a good software development team not only has good collision and communication with each other, but also can accurately budget the progress of the software project.

The cathedral and the bazaar convincingly illustrate the Tovac-style open source code as a leap forward. Raymond shows how open markets can melt the wisdom of large groups of programmers in a furnace without touching the law of Brooks, but he cannot tell whether open source is more likely to predict how long it will take to develop new programs or to speed up the process of software availability. However, the cathedral and Bazaar did not really refute the Brooks law, nor did it solve the problem of software development time.

"Dream Break Code" 1