Dream Break Code Reading Note 3

Eighth: Instant stickers on the whiteboard
What is an instant sticker? The answer is to use a sticker. Each piece of paper represents roughly the same amount of work. Each instant sticker represents a single developer for one months or two months of work. Now the walls are pasted in the order of the dots, and then you can see how each round of planning works and whether you are out of reality.
talking about here, I think of what Mr. Wang said, indeed, in the process of development, we may appear to deviate from the original plan, after all, development needs creativity, we will inevitably forget beginner's mind.
Mr. Wang confessed to our team to develop the task is also need to put on the whiteboard, write what, how to write is very important, this is related to our development process has no resources waste.
first of all, the area of the whiteboard is divided into one side to discuss the task name, paste location, whether some of the particularly difficult tasks to be divided into two pages and so on.
Nineth Chapter: Methods
What is the method? Methodologies can be seen as a recipe for the success of a software project as a freeze-drying process. Some programmers rely on methodologies, sometimes at the end, sometimes in mixed use. and many others refuse to let their unique talents succumb to any rules.
everyone wants to succeed, but failure is not necessarily the mother of success, and failure is likely to fail again.
success is some process, we must follow the plan, step by step.
Project management guru Watzhanfrie The proposition that "more plans must be made." "As long as the individual developer part of the individual work plan and follow it, the project will be uncontrollable and not manageable." "
We all work for the organization.
The organization needs a plan.
unless your work is independent enough, you must work on schedule.
If you don't make your own schedule, people will arrange it for you.
so that others will control your work.
The above is a valuable experience that should be followed.
We explore software development methods in practice, and also help others, building the following values: individuals and interactions above processes and tools
working software is more than detailed documentation
customer cooperation is higher than contract negotiation
response change is higher than following plan
Tenth chapter: engineers and artists
There was an article called "The Humble programmer," and there was a phrase: "Good programmers know that their abilities are limited, so his attitude towards programming tasks is completely humble, and in particular, they will escape the ' clever tricks ' like escaping the plague."
(a car brakes failed, fell off a cliff, project experience, hardware engineer and software engineer dialogue: The software engineer said, before the start, I think the car should be pushed back to the mountain to see if the accident will reappear!!! ON) If you report a defect to the programmer, his first response is to ask you: "Reproduce the problem?" --meaning, can you really make the problem recur? If the answer is yes, it's half the story, and if it's negative, the programmer shrugs and puts the blame on the hardware or cosmic rays! We met the bug also first asked can reproduce, but more ...
writing a program, this sentence is worth pausing to ponder. So is programming a project or a literature? Is it science or art? How to solve the double problem of programming becomes the confusion of many people in the field of reform. ,
Gartner, who won the Turing Award in 1984, said: ' Computer programming is an art '. What art is, art is what human wisdom does, as opposed to natural or instinctive behavior.
 
the 11th chapter: the way to the dog food edition
Each extension of chandle is nothing to itself, but as the album program of Morgan Thatch does, each extension injects vitality into its initial commitment. These expansions, and their ability to put seemingly disparate information together almost effortlessly, won a cry of exclamation.
software is really hard to do, with the author's three years of software time experience, despite exciting new methodologies, taboos and groundbreaking ideas. But, there are different categories of difficulties. It is difficult to raise a child, to bury first, to be born and to grow, to live with or no one, to try to love, to love, to accept the death of others, to accept his death.
software, that is another difficult world, compared with life, not too difficult one.
Concluding remarks:
by reading this book, let me have a new understanding of software development, at the same time, also picked up the feeling that I read the paper books many years ago, every night, a lamp such as beans, outside the curtain is like the night of ink, the heart will go with the author, as experienced a battle.  And the book and Sleep, suddenly awakened, Huangrugeshi.

Dream Break Code reading Note 3