Since September forgot to write book reports, leading to fill before October should read the report.
"The Pragmatic Programmer - from small work to the experts' point of inspiration of this book is always interesting to look at my old ideas, I always thought that these books would be very dull, sleepy read . But otherwise, this book is full of not only dry, but also with some interesting stories to illustrate the truth. For example Cook stone, boiled frog. Program, the programmer to write out. It is based on the idea of people produced. So, I want to write the code, must first correct their thinking. Nor is it correct, that is, some of the details out of their own thinking and mentality. So the front part of the book is how to write regular themselves,
First, they must be responsible for their actions. Future work in the company, it is inevitable there will be large and small things. For example, your source is a problem, but there may not be causing you. These errors do not pass the buck to someone else, your colleagues and the so-called "cat" are innocent. Wrong is in you. A sense of responsibility. Rather than a student you explain the cause of things after the results there will guide you let your members understand. Into the community, to be responsible for their actions, if not responsible, it would be ready ahead of time, the source backup, what documents to back up. Preparatory work done, and there would be no worry concerns.
Work must be neat and tidy. Your code has Anbing, unsightly irregularities, which not only affects you, but will also affect your team or even your company. Just like our Jianmin Obama told us, we are now compiled code are small case, are compiled in our greenhouse, some small problems is not sufficient to cause any effect, we will come to the company, a few large projects one hundred packets thousands of source code, this time once a little flaws, such as the interface out of the question, the whole program will crash. Like an avalanche, no snowflake is innocent. Your mistakes add up to snow-capped mountains, at the moment it has been able to stop the collapse. So, then again, do a good job at the source, most of the trouble after waived.
The world is not an absolute good software, all software development are in progress, and customers to communicate, he wanted to achieve what extent, and only reached the demand is not enough, we must also consider the quality of the code. This should be an important point and client communication. Not only to learn and customers, and the same group of people, and the industry's heavyweights exchange is more important. Gangster and communication, this is not a meaningless social, this is very important for their growth. And more talk about professional knowledge, experience his thoughts, as compared with their own ideas, we can not shut ourselves up. Well people, nor is it to live in a vacuum. And people still want to communicate.
When using a search engine, multi-screening information meets their requirements. Here personally I recommend Google, Baidu than professional strengths. And some master's doctoral dissertation to write what are more like to use Google to search for information. Be concise written in their search target search Shihai. Be humble when to ask for help on the Web, you can also send mail to the experts what some executives directly, but also pay attention to the official of the speech.
The following is the advice given in the book:
- At least learn a new language every year . Different languages in different ways to solve the same problem. Through a number of different ways of learning, can help you broaden your thinking and avoid legalistic In addition, many are now learning the language has been a lot easier, thanks to the wealth of software freely available from the Internet
- Quarterly reading an art book box . Many bookstores are filled with books, and discuss interesting topics related to your current project. Once you develop the habit, I read a book a month. After you have mastered the technology you're using, widening the scope, read some not related to your project books.
- To read non-technical book box . Remember computer by someone - you're trying to meet the needs of its people - to use, which is very important. Do not forget that the human side of the equation.
- Class . In the local college or university, or the next will come the time to find interesting subjects on exhibition
- Participate in local user groups . Do not just go to listen, but to actively participate. Isolation of your career, it can be fatal; inquire about people outside the company you are doing.
- Experiment with different environments . If you only work on Windows f at home to play with Unix (Linux freely available on the right) and if you only used makefile editor, you try IDET and vice versa.
- Keep up with trends . Subscribe to technical and business magazines and other periodicals covered with your choice of current projects in different publications.
- Internet . Ah want something new language solution or various characteristics of other technologies? To learn about other people's experience, so that they understand
Specific jargon used, and so on, newsgroups are a good way. b Net surfing t find papers, commercial sites, as well as itsHe any source of information you can find.