"Dream Break Code" reading comprehension One

In fact, I should have sent this one, I have read the two chapters around the sentiment, and my whole book is almost finished and has not been sent. I always feel no sentiment, just mechanical reading. Think, I still can not really think of themselves as a qualified computer industry practitioners, I am very difficult to understand the book programmer Ordinary in the extraordinary.

In this book, as long as the development is bound to have a team, although not specifically emphasized, but it is clear to tell me that the development of the program is a team project, single-fight is not suitable for the current trend. I have always been more inclined to teamwork, only a complementary team will let the individual strength fully demonstrated, with a companion, will be faster to find their mistakes and shortcomings.

The book mentions a lot of problems encountered in development, from which I found that many of the problems I once thought were not enough to cause the problem is mainly that the beginning of the idea is not correct or too complex, want to solve all the problems will often lead to the failure of the program.

may not be able to fully write the reading of the sentiment, but this is a preparation for programming work rather than programming to make money the true sentiment of the people.

"Dream Break Code" reading comprehension One