The way of programmer's cultivation--from small work to expert

" of all the weaknesses, the biggest weakness is the fear of exposing weaknesses. "I love this sentence. This let me remind myself once again, do not be afraid to expose their own mistakes to others, do not be afraid to expose their ignorance to others. Only expose the shortcomings, can let others see, and help themselves to correct, they will ascend.

The first chapter of this book tells us the importance of responsibility and reminds us not to keep "broken windows" (poor design, wrong decisions, bad code) from being repaired. The story of Stone Soup and boiled frog tells us the strength of unity, do not neglect small things, always pay attention to what is happening around you, don't confine yourself to what you are doing. This is also my own to pay attention to the problem.

"The desire is better, often the good things get worse." I have a good understanding of this sentence, in programming, often in order to make the program approach perfect, after the program is written to modify, the results often changed the program, even the original function can not be achieved. When learning to stop, the program is not perfect.

As programmers, their knowledge of computer technology, all the facts of the field of work and the experience they use are their own intellectual assets. Run your own assets, invest regularly in your assets, acquire more technology, seize opportunities, and don't mind learning about new technologies before they pop. This book gives us some ways to raise our own money: learn at least one new language each year, read a technical book quarterly, read non-technical books, attend classes, participate in local user organizations, experiment with different environments, keep up with the trends, and surf the internet. This is a big reminder to me that I do not love reading, even if the internet is not enough patience to read those scientific papers, technical papers. Pay more attention to it later.

Communication is also important in programming development. Communicate with users, understand their needs, communicate with machines, communicate our intentions, communicate with other developers and get to know each other's ideas. Express your ideas completely and let your listeners know what they mean.

In my opinion, these are very important to us now, and we should always face them.

As programmers, we collect, organize, maintain, and utilize knowledge, we document knowledge in the specification, and make it active in running code and used to provide the checks required during testing. Knowledge is unstable, and we need to spend a lot of time on maintenance, re-organizing and expressing knowledge in our systems.

The second chapter describes the problem of repetition, and proposes a general strategy to deal with it. Repetition is divided into repetitive, unintentional repetition, patient-free repetition, and duplication between developers. The whole book frequently mentions the dry principle: every knowledge in the system must have a single, non-discriminatory, authoritative expression. By writing an orthogonal system, there are two main benefits: increased productivity and reduced risk. Maintain orthogonality: Keep your code decoupled, avoid using global data, and avoid writing similar functions.

The way of programmer's cultivation--from small work to expert