Dream Break Code read Note two (chapter 4-7)

In the last week, "Dream Break Code" finished reading the seventh chapter, the book has more than half, for the books have a deeper understanding of the difficulty of software development is more understandable.
The Le Gao Wang Chapter introduces a code world or a good idea in the programmer world--the program will be made up of reusable components, software components will be available worldwide, and software engineering will be freed from the programming rut. Software components, like Lego bricks, are small, no longer able to be divided, can be substituted, and can be freely combined. This is the concept of code reuse, which eliminates the hassle of writing code, but there are many problems, such as the scarcity of large reusable components, and the reluctance of some programmers to merely and so on. In fact, I think this is a good idea, but also a direction worth the effort. Because most of the time we write code that is known to be a waste of the day, we should spend more time innovating the code or creating new combinations in the existing code parts. This chapter also tells the OSAF gathered a group of more aspects of the elite development Chandler, but the difficulties, the process often deadlock, you can see the difficulty of software development.
The fifth chapter of the topic is very interesting, is "Control geek and Dog", a look at the topic completely do not know what to say, after reading to know that the word geek is used to describe those who communicate with the computer easy to communicate with human beings, while the dog refers to the staff at that time in Osaf's pet dog, this chapter is these management issues. This statement behind the point is one of the important issues of software project development, the completion of the project in addition to writing good software, but also to manage the people involved. In other people's eyes, programmers have some quirks of character, some of them are so, so need management talent will these programmers "appropriate development", so that they can better collaborate in the team, and play the greatest potential.
The sixth chapter feel said a lot of things, in addition to the topic of the design, there are user experience, product artistry and so on. Design plan for large-scale project development is very important, in fact, for us, in peacetime programming should also form the habit of designing a good plan, most of us are writing side design, so that the overall mentality is more chaotic. User experience and product artistry for product recognition is also important, the software is ultimately to deliver user use, the user will not care or understand the code is how excellent, the key is the product of the friendly interface and the use of comfort, artistry will also improve quality.
In the detail view chapter, I see the Chandler Project's Quest for detail views. The beginning of this chapter mentions the small progress of the project, the release of the new version, although none of it is available, just to satisfy the interest of external software developers who may be curious about the progress of the company and its team, but the atmosphere inside the OSAF is completely different. When a long-term helpless project has a breakthrough, it is exciting for the whole team. At the same time we see the detail view of the importance of software projects, usually we think as long as the code is written well, in fact, the actual delivery of the user's software in the view is also very strict requirements.
The whole book is scheduled to be read around next week, hoping for a bigger harvest eventually.

Dream Break Code read Note two (chapter 4-7)