Introduction - If you have any usage issues, please Google them yourself
Programming specification
Several principles of programming specification
1. Programmers spend more time debugging, maintaining and upgrading existing code than writing new code;
2. The most important part of the program is correctness, the second is maintainability, and finally the efficiency;
3. Learning how to write beautiful programs is just as important as learning how to write code correctly;
4. Make the program as simple and understandable as possible, even if it violates certain rules.
A program that runs normally but doesn't annotate is like a time bomb waiting for an explosion, because sooner or later someone modifies or upgrades the program;
6. Good style should become a habit. If you care about style when you start writing code, if you take the time to review and improve it, you'll gradually develop a good programming habit. Once this habit becomes automatic, your subconscious mind will help you take care of many details, and even the code you write under pressure will be better.