Best practices for software developers

I recently saw an article on a website about how many practices software developers should have. I feel that the article is well written. The following sections describe the following aspects.

First of all, the article puts forward that software developers need to keep practicing, what is practice, why is practice, and what is practice? The article provides a very good explanation. Exercise is a habit. Exercise is a process. practice does not mean that you must keep yourself in mind. Exercise requires constant practice. Shooting athletes need to constantly practice to hit a lot of other scores, driving also need to constantly practice to become a driver, writing needs to constantly practice to write good words, and then may become a calligrapher.

Shooting, driving, writing

 

Best Practice 1-Keep reading existing software sourcecode

Do you often read the code of Open Source Software? It may be considered a very boring thing. A novelist becomes a novelist only after reading hundreds of excellent novels. Therefore, to write excellent code, you must read thousands of lines of code.

Best Practice 2-complete your documents before next step

In the development of large-scale software, the analysis documentation is very important. Only by figuring out what needs to be analyzed can we proceed with the next development. Before development, we need to ask ourselves the following questions:

• 1. Where is the description of software requirements?
• 2. Where is the software design document?
• 3. Are you clear about all the descriptions of conditions and conditions?
• 4. Have you reviewed all documents?

...

Assuming that you have answered the above questions, you can perform the next step. coding, many companies have a complete set of development processes to ensure the correct implementation of each link.

 

Best Practice 3-follow the defined standards, Don 'tcreate it

In the software development process, you must follow the existing standards and do not create your own style. At this point, many companies have their own programming standards, which may be recognized by the industry and may also be the best practices of the developers after years of summarization. One sentence is very good. Following the footprints of our predecessors often leads to less detours. These standards may include the following:

File naming rules, function and module naming rules, variable naming rules, readability and security rules.

Clean, neat, and consistent, and beautiful are important features of source code readability and comprehension. Remember one sentence: source code is your baby.

Best Practice 4-code shocould be written to be reviewed.

Readability is often the most intuitive embodiment of source programs. When we write code, we always need to remember that some people will always review the code we write, and we will face various defects, such as: bad coding style, failing to follow standards, the Function Definition and gaze are not standardized, the readability is poor, the opened file is not closed, the allocated memory is not released, too many global variables, too much hard coding, and too much repeated code. When coding, always remember the above problems. When coding is completed, at least you need to check it again, which can often reduce the error by 90%.

I like one sentence very much: Accept criticism but don't criticize! When the code we write is worse than coding, we need to accept the problems pointed out in the peer review. If others give it to ourselves, it does not mean criticism, but it is better to improve ourselves, fewer mistakes will be made later. In fact, review is also a crucial part of the development process. As a developer, you also need to look at the problem from the perspective of the subject, so as to reduce the occurrence of errors.

Best practice 5-testing to be followed like a religion.

Every time you write the code, you need to perform a trial. No matter you are an experienced developer or a newbie, you must pass the license test for every code change. We must:

• Don't compromise on the trial.
• Modify a row and stare at it.
• Modify the name of a variable.
• If you think it is unnecessary, it is critical.

Best Practice 6-keep your code and documents safely.

This is mainly to prevent code and document loss. We need to develop the habit of backing up documents every day. Everyone may think it is more complicated than prepare. We recommend that you use the date, time, and version for backup.

Best Practice 7-keep your tools & TECHNIQUES handy

As the saying goes, to do good deeds, you must first sharpen your tools. For developers, good tools and skills can improve our efficiency and reduce the chance of errors. For example:

• 1. Use a good editing tool to write and modify code
• 2. Use a good debugger to debug the code
• 3. Use a memory monitor to dynamically allocate memory
• 4. Use winscp or filezilla to transmit files.

 

Best practice 8-Leave the ego behind, be eager to learn.

I think this is more important than others. We often obtain knowledge from books and the Internet. However, no one in it can grasp all the knowledge in any field, every day, we are faced with various problems. In order to keep yourself from falling behind, you must always learn.

New technologies are coming everyday

 

There may be no shortcuts to success, and a hundred times of effort is required to succeed. Today, you have paid a little bit, which is closer to the road to success.

Best practices for software developers