The legacy of the programmer's father-the Ten Commandments of programming

My father died after two weeks of programming with me. At that time, I was 22 years old, a senior student who had just finished the Bachelor of Aesthetics graduation design. My father, 62 years old, is older than most of my peers ' fathers. As early as the 60 's, he started programming languages at the Tennessee Tech University, when he wrote Fortran on punched cards. I have to admit that my father is educated player and knowledgeable. The first time I was in touch with the program, it was like fireworks, and suddenly it was my life. It gives me a sense of magic and power, and in many ways more creative and practical than visual design. When I came home on holiday, my father shared his "Cheng". He printed a copy and then discussed it with me in one piece. It was one of the few discussions about programming between me and my father, and then he suddenly left me. Perhaps also for this reason, this "knitting Cheng" deeply engraved in my mind, and that day my father's likeness together, become my best memories, rock no transfer. Inspired by the first release of the Psychology of Computer programming in 1971, the following is the Ten Commandments of programming that my father summed up: 1. Understand and admit that you can make mistakes. The key to this point is to find out earlier before publishing. Fortunately, few errors are fatal unless you are developing rocket guidance software in a Jet propulsion lab. So, after making a mistake, we can learn lessons from it, and then maintain a positive attitude and continue to move forward. 2. Err, who can have no. The purpose of reviewing the code is to find the problem. However, if there are omissions, the blame should not be attributed to a person to go against him. 3. There are people outside, heavens beyond heavens. A three-person will have my teacher, ask a mentor, will make you benefit. Learn to listen to other people's opinions and suggestions, especially when you think that there is no need, but also with a modest attitude, a broad mind to accept the advice of others. 4. Think twice about refactoring your code. There is an essential difference between "fix code" and "Refactoring Code". After careful deliberation, if you still want to pursue code review when the framework style can change, rather than along the original path to improve, then refactor it. 5. Respect for others, patience, courtesy to everyone. Non-technical people who often deal with developers often find programmers defiant, grumpy and smelly. Don't let your anger and lack of patience make the image in their hearts grow taller. 6. The only constant in the world is change. Open-minded and smile to accept change. Take every change in demand, on the platform, and in the tools as a new challenge, rather than as a nuisance to resist. 7. Real authority comes from knowledge, not position. Knowledge makes authority, authority brings respect-so if you want to be respected by others in the field of computing, learn. 8. Strive for faith and then gracefully accept defeat. Sometimes our ideas are going to beVeto. Even if it turns out that we are right, there is no resentment, or something like, "I've said this before, I don't believe it." Don't let the team create a gap between them, do not dwell on this trivial matter, often complain. 9. Don't be a "programmer in the Corner". Don't be the kind of person that hides in an obscure corner of the office and comes out at the point of a meal. Hiding in the corner programmers are often short-sighted, isolated, and disconnected from everyone. They will be like invisible people without any comment. Therefore, to participate in the discussion, to become a member of the Office of the Coordination of the Group. 10. Can criticize the code, but not personal attacks should be friendly to each programmer, but in pointing out the problem can be sharp, sharply. Our criticisms should be as positive as possible and aim to improve the code, not aimless. At the same time, local standards, procedural specifications and improved performance should also be considered. So far I have kept this copy of the Cheng. As mentioned above, I grew up to be a good programmer. Sometimes, I can not help but think, if my father is still there, what advice will he give me? Though this has become a delusion, I believe my dear father will be proud of the 10 commandments that I have always kept in mind. Free to receive the Lamp Brothers and original PHP tutorial CD/"Detailed PHP" Essentials Edition, details of the inquiry website customer Service: http://www.lampbrother.net

