"Dream Break Code" book (1)

Dream Break Code

Read "Dream break code" for a certain time, read nearly half of the content of this book also has a preliminary understanding, began to choose to read the name of the book when I think of a classic movie called "Soul Broken Blue Bridge" so I did not hesitate to choose this book, see before I first read the review of the online reviews are also good , also know that this book is mainly about Chandler long and painful development process, began to read this book also let me learn a lot.

The beginning of the book begins with the No. 0 chapter, the author's explanation is a computer programmer from the 0 technology which is also a habit, I think this opening is very good, as a programmer will be accustomed to count from 0, so I am also gradually interested in this book. Chandler the long development process from the development of the software process encountered problems and solutions to give us a lot of experience and a lot of useful knowledge. Chandler is an open source project developed by OSAF. Unlike other commercial software, Chandler's development process lacks that "strong" management and discipline, and almost no one is responsible for the entire project until a year after the project begins, a software development manager is there. All the members of the project should play their own creativity as far as possible, the beginning of the idea is very good, have their own goals and the main development of the project needs, but with the continuous improvement of the demand and problems of the development of the project has also appeared a certain problem, see now this book to my help is still very big.

This book talk about Chandler development process also mentioned a lot of development software encountered problems and solutions, at the same time give a lot of programming ideas are worthy of our reference, in the process of reading is a bit dull but the harvest is a lot, whether it is knowledge or thinking is very good learning materials, Software development is not as simple as imagined, it involves a lot of aspects of the development of the software is not suitable for the failure, so in the software development process to constantly check and maintenance to ensure that the normal development and normal operation of the software.

"Dream Broken Code" is a good book, it can give us a lot to learn from and learning aspects, he gave us is the real experience and lessons, we learned is valuable experience and ideas, told us in the team to develop software to cooperate with each other's importance, taught us a lot of attention in team development, I've got too much to gain from it.

"Dream Break Code" book (1)