3. Correlates with the second part of the first principle. No thought of the end of the work, no thought of money or prestige should occupy the programmer's head even in Terminate but Stay Resident mode. The programmer's memory must be fully given to the program while working on the program. Experience has shown that any extraneous thoughts ultimately only interfere with the program. What should I do if I still have thoughts? Either do autotraining; or find a better job; or find a way around
the uninteresting place in the program or make it interesting; or do nothing with the knowledge that you work slower and worse than you could; or stand a break.
4. In ancient times, it was believed that programming began with drawing block diagrams. Experience shows that one should start programming long before and finish it much later than the stage of working with the program text itself. This principle of work is deep. What do you actually want to say with your program? Do you have enough strength, means and resources? Hasn't it been written by others for a long time? Will someone need it after it has taken on a commercial form? Will someone else be able to buy it, provided that you have produced it for sale? And, again, if you expect to sell your program, as well as for how much you will sell it?
All these and many other questions can affect the text of your program.
5. This is something you should strive for. This is a true art.
6. Every programmer either has an opinion about a good program, or has ever heard of someone else. Pascal writers try not to use the GOTO operator and talk about the indents. Writers on the CI try to place no more than one procedure on the screen. Writers who write in assembler language are not only isolated in operators, but also in comments. And so on. All this is essential if you are not writing a program for sale. In this case you just write the program. You don't have to follow the principle of "programming". Another thing is to program a commodity software product. The text of the product program may be beautiful, but time is usually against beauty.
The buyer is guided by very different criteria than the beauty of the source code. On the other hand, a beautifully written program is more convenient from the viewpoint of debugging, contains fewer logical errors and usually works more reliably. The only way out is to write beautifully at once.
7. This is the only way. If you don't understand why other answers are inadmissible yet, you should still answer one of the two suggested ways without hesitation.
8. Games, antiviruses, NORTON COMMANDER and other residents, drivers ALFA and BETA should be removed from memory, if not from the hard drive. These are childhood diseases. As for the game TETRIS, it is the best computer game, but still tedious.
9. this principle can be called the deepest. Oh, how many months and years have spent on writing programs that have long been written.
One truly attentive reading of the MS-DOS manual will save you from many and many disappointments and unpleasant discoveries.
10. You can be a programmer and not write programs. You cannot stay a programmer for a long time without reading the documentation. Printing of dumps is not necessary as much as it is not necessary to open the hood of your own car (viewing of dumps on the screen is a half-measure). It is impossible to program without sleeping. If you are not a programmer, but the head of the programmers and make them come to work by a certain date, then you lose the programmers and get stuffed with incomprehensible texts.
11. this is one of the postulates of information theory. The present programmer is able to use in the work all information which is at his disposal at present on the given question. Any book the programmer reads also as documentation and extracts information on programming from any printed edition.
12. The comment on Principle 10 may seem gloomy, but fortunately the actions described in it are only necessary, but not sufficient. The programmer does not live to work and does not work to live. All misunderstandings arise from ignorance of the fact that the programmer's working tool is, besides his head, his soul and aesthetic sense.
13. A purely stylistic element. Illustrates the fact that the price of a system that does not have the opportunity for development is a penny.