"Dream Break Code" 1th Chapter reading notes

This note was published late ( i don't know why .) The site you are trying to access is rejected based on your organization's Internet access policy. If you have questions, contact your network administrator. "), the reason why you are lazy or time is not so rich may have it! Just programmed to achieve the teacher left a part of the program function, just relax your mind to write this note.

Have to say is the first chapter I see a bit dizzy feeling, this is also I have not been quiet down to write this note one of the reasons for it. In the future can not do so, as far as possible to release notes as early as the law.

"Dead" has to say that this is a very attractive topic, in the end why the dead? It turns out they're all dead--the programmers! They were pained by their inability to complete their task in time. They were talking about why they couldn't finish the project on time, and it was from their words that I learned about the approximate process and work steps of the software engineering work.

"There is a blueprint", indeed, the blind work is how ignorant behavior, especially software engineering this need to clear division of labor and unified coordination work. How can you just figure it out quickly and blindly. It's like having a plan in our work and life.

What Jede Burgiss said gave me a better understanding of the Software engineering project-"There are too many uncertainties: the time you need depends on the time that other people spend." "Indeed, we must learn to cooperate with others to make reasonable arrangements for the time and distribution of work." Each programmer will have a ballpark estimate of the time it takes to solve a problem, which is also an important basis for assigning and assigning time to work.

But in programming, there are many uncertainties, and we always have to be prepared.

The Brooks law is also something I should write down: the addition of manpower to projects that have been delayed will only cause them to continue to be delayed. Even if some people pretend that the law is not suitable for themselves, it is true. People's month is not equivalent, only the task can be assigned to many people who do not communicate with each other, the person and the month is interchangeable goods. It can be seen that software engineering projects do not rely on more people to complete the good, only a tacit understanding of the group, in the right time to complete a good work.

The stories of closed software and open source advocates are described in the following chapters. I prefer open source advocates, allowing free software to carry forward the process of software development from a small number of hermit's hands, spread to the vast crowd.

"Good software development starts with building the developer himself. "As long as you are doing something that you can satisfy or please yourself, the programmer will be full of power." Really interested in the key Ah, later programming also want to find their own interests.

There is another law, "the eyeball is enough, the defect is nowhere to be hid"--Linus law. More people can find a software problem.

"Enjoyment is efficient", "pleasure is gold" idealized motto is exciting, but still need to practice. "The hardest part of building software is deciding what to say, not how to say it." "The success of Open source tells us that play is the most cost-effective way to work creatively. It seems to the software world I understand is too little, hoping to learn from the books in some, reading the fun and motivation may be in this bar.

"Dream Break Code" 1th Chapter reading notes