"Dream Break Code" 4–5 reading notes

Front desk dialogue with people, backstage and bit dialogue, concise.
Create or reuse? Every software will arrive at this fork in the road sooner or later. Indeed, we are not the same, reuse is convenient and simple, but whether it is completely suitable for their own
The programming environment is still an unknown. While creating a time-consuming but undoubtedly against their own situation, both have advantages and disadvantages.
Looking forward to the future that the program can be reused parts, software components will be available on a global scale, so we may say goodbye to the painful programming process, only to enjoy the joy of success.
The too many standards of the software community, perhaps, are a big hurdle to reusing code.
"Programmers always take pride in their creations, calling them merely, which is tantamount to the Buddha's inverse scales." "True, originality is great, but we want good results, because users are not going to see your program,
Many people are standing on the shoulders of giants have achieved success, why can't we?
The development of a software, like human growth-adults, growth, learning and development, toward the perfect change themselves.

Ability to quickly learn uncommon or special skills. If the discipline is lax, the director will be teased. Is that a Labrador poodle or a programmer? The similarity between the "manager" and the "master" is staggering.
Programmers are stubborn lone-amuse his, not enough to promote their own, they need to touch and caress, to have rats to kill, to have defects can clean up. It seems that the programmer's management also has a very advanced
Connotation.
The old saying is good: fast, cheap, high-quality, choose the second bar. It seems unlikely that the three are both.
Make a progress plan and try to keep up. Simple but practical, as long as you insist to do.
Geek: A person who focuses on his own business, who pursues technology (especially expertise) and dreams, and does not integrate into the mainstream society. Such people have a dream to pursue, have a clear goal, it should be the people we learn.
It's a little harder to communicate with IT professionals than the dead. This is not enough, I hope I will not do so.
Programmers, though not gregarious, really need to talk to others-the more casual the form, the better.
In software management, collaboration is not an afterthought or a trivial matter: it is at the heart of the work, and deciding which tools and methods to use may make or break the project.
Give me 6 hours to cut the tree, I will use the first 4 hours grinding axe. Preparation and planning are important and cannot be programmed blindly.

"Dream Break Code" 4–5 reading notes