Summary of common mistakes made by. net developers

1. We think that Visual Studio. NET must be used to develop. NET applications. 
Those who do not know about Microsoft. NET development mistakenly think that Visual Studio. NET must be used to develop application software using the. NET Framework. This is not correct. You only need to install the. NET Framework that can be downloaded for free on the Microsoft website.

After installing the. NET Framework, you can use your favorite text editor and. NET tool command line for development. You can also apply third-party development tools, such as SharpDevelop.

For more information about Visual Studio. NET, see previous sections. The selection of development tools varies from person to person, but many development teams are standardized to simplify the work.

2. Exclusive Information
One of the notable features of developers is that they tend to store confidential information. The ability that people do not know often leads to incorrect superiority. On the contrary, sharing information helps the team expand their knowledge. In addition, the information shared with other team members can be improved. Finally, when you explain a concept or idea to another developer or a group of developers, your knowledge is also expanded.

The spirit of teamwork is the driving force behind movements such as Agile Software Development. In addition, many teams use peer code reviews (peer code reviews), which enables developers to review and comment on the code of other developers. This approach facilitates both parties to learn and understand the code.

3. Ignore code comments
Adding comments to your code is a simple and direct method, but why do you always ignore this? Some developers mistakenly believe that the reduction of file proofs (in any form) can improve work security. This is the same as exclusive information discussed earlier.

A few reasonable annotations can greatly improve the readability of the code and facilitate code management. There is a tendency to use annotations too much. Basically, these annotations should be briefly described in terms of code, variables, and methods. Many teams prefer to insert comments when making changes to the Code. When a problem occurs, it is easy to find out which modifications have been made before.

4. The value of the version control system is not displayed. 
Most developers are very familiar with this situation: When you launch a new version of an important network application, your mobile phone keeps ringing early the next morning, and it is full of website problems.

If you are willing to admit that you may have made one or two mistakes, in this case, the version control system is your best friend. By using version control systems such as CVS, IBM Rational ClearCase, and Microsoft Visual SourceSafe, you can easily restore to previous versions of application software for production. This allows you to find out the problem in the development environment when the production site is ready. This method is much better than finding the problem by searching for production code.

In addition, the source control system allows different team members to develop the same code at the same time. These changes are combined when the developer checks the modifications made to the system.

One of the reasons why some developers do not like the version control system is that it adds a step to the development process, which means that the process of submitting code to the source control system and restoring the Code through it slows down. This extra wait time has hit the patience of some developers.

5. All projects require Network Services 
Due to the excessive publicity of network services, many developers believe that network services must be used in some form in development projects. Although the use of network services during development may be necessary or appropriate, it is not entirely possible. You need to analyze different situations to determine whether the execution of network services is appropriate. For example, remoting may be more appropriate.

6. Ignoring the importance of validation data
In application code, data is processed in different forms. For this reason, developers should confirm data integrity and effectiveness during the development process. That is to say, the data should be read through the terminal database that can return zero characters. Check the data before execution, because zero value cannot be used in most operations.

Half of success
Whether you are new recruits or veterans, you must be aware that developers are making these six mistakes. Even if you discover that you do not have these bad habits, you must be aware that other developers in your team may make these mistakes. Be cautious with these potential errors to prevent them from interfering with your team's plans.