Best software development practices in history

Every time, I can read some good things. They are so profound insights, so clearly written and organized, I must include it in my personal "Best in history" collection. Recently, I have added a new article titled best practices for scientific computing.ArticleI hope every reader who reads this article will find time to read it. I will list the key points here to encourage you to read the full text. I wrote very well.

2. Write to personProgramInstead of the computer.
   1. A program, for those who read it, should not require the reader to load too much background/related knowledge in the brain at a time.
   2. Naming must be consistent, clear, and meaningful
   3. CodeConsistent style and format
   4. Various tasks in software development must be divided into tasks of about one hour.
4. Automated repetitive work.
   1. Let the computer do repetitive work
   2. Save recently used commands to a file for reuse.
   3. Use compilation tools to automate System Processes
6. Use a computer to record history
   1. Use software tools to automatically track computer work
8. Gradually improve.
   1. Every time you take a small step, get feedback in a timely manner, and correct it in a timely manner
10. Use version control.
    1. Use a version control system
    2. All manually created items must be put in the version control system.
12. Do not repeat yourself (or others ).
    1. Each piece of data in the system must have an authoritative and single existence.
    2. Code should be modularized and reused, instead of sticking to it.
    3. Reuse code instead of rewriting code
14. Prepare methods to handle errors
    1. Add assertions in the program to check their various operations
    2. Use a ready-made unit test framework
    3. Learn from all available experiences when testing programs
    4. Build bugs into test cases
    5. Use a debugging tool with code instructions
16. Optimization is only possible after the software works properly.
    1. Use monitoring tools to locate bottlenecks
    2. Write programs in advanced languages as much as possible
18. The document describes the design philosophy and purpose, rather than the technical details.
    1. Describe interfaces and causes, rather than implementation
    2. Refactor the code, instead of commenting on the running principle
    3. Documents embedded in other programs when referencing other programs
20. Collaboration
    1. Code review before code Merging
    2. Use Pair programming when it helps bring new members or solve especially strange problems

Here is an additional reference:

11. Restore the old code.

If you are still wondering whether to read the article, check out the 67 books and articles on computers listed in it. As I said, this article is "the best in history ".

Original ENGLISH: Best practices ever

Http://www.aqee.net/best-best-practices-ever/.