真正的程序员（real programmer）.doc

真正的程序员（real programmer） Software quality is the majority of programmers have paid lip service rather than the heart! In addition to being a complete layman and a real master of programming, your first reading of the book will be a panic: Wow! How can I have so many problems with the C++/C program Ive made up before? Dont be sad, the author is only a few years and a few times earlier than you panic. Please spend one or two hours reading this 100 pages of Scripture carefully, and you will benefit a lot from it. This is a suggestion from the previous N-1 readers. First, programming veteran and master misunderstanding Since the invention of the computer, the program design has become an enviable occupation, after the programmer loved by the people likely to develop into problems of Trinidad and Tobago are often groups of self smug. Today, real programmers on Internet are said to be like this: (1) real programmers do not have schedules, and only those who flatter their leaders have schedules. Real programmers can keep their leaders on tenterhooks. (2) real programmers do not write instruction manuals, and users should guess the functions of the program themselves. (3) real programmers hardly write code annotations; and if the annotation is hard to write, its certainly hard to read. (4) real programmers do not draw flowcharts; primitive and illiterate people do it. (5) Real Programmers dont look at the reference manuals. Novices and wimps look at them. (6) real programmers do not write documents, nor do they need documents. Only those who do not understand the program can use them. (7) Real Programmers think they know what the user needs more than the user. (8) real programmers do not accept the idea of team development unless he is the head of the team. (9) real programmers in the program will not be correctly the first time, but they are willing to keep the machine several 30 hour debugging error. (10) Real Programmers dont work between 9:00 a.m. and 5:00 p.m., and if y