Avoid six common development errors

Tony Patton wrote an article on ZDNet, titled "Avoid Six Common development mistakes", read it and feel good, shrink it and post it.

1. Think you have to use Visual Studio.NET to develop. NET applications

You just have to install it for free on the Microsoft website. NET Framework. has been installed. NET Framework, you can apply your favorite text editor and. NET tools command line for development. And, you can also apply third-party development tools, such as SharpDevelop.

2. Exclusive information

One of the salient features of developers is that they tend to hide information. The ability of Xiao people not to dawn often causes the wrong superiority. On the contrary, sharing information helps the team expand their knowledge. In addition, the information you share can be improved as other team members join. Finally, when you explain an idea or idea to another or a group of developers, your knowledge is expanded.

Team spirit is the driving force of Agile Software Development and other sports. In addition, many teams use peer code reviews, which is a way for developers to review and comment on other developers ' code, which facilitates both learning and understanding.

3. Ignore code comments

Commenting on your own code is a simple and straightforward approach, but why do people always ignore it? Some developers mistakenly believe that reducing documentation (in any form) can improve job security. This is a fallacy, as is the exclusive information discussed earlier.

A few reasonably arranged annotations can greatly improve the readability of the Code and facilitate the management of the code. Now there is a tendency to use annotations too much. Basically, these comments should be a brief description of the code, variables, methods, and so on. Many teams like to insert comments when they make changes to the code. When (if) there is a problem, we can easily find out what changes have been made before.

4. Not seeing the value of the version control system

Most developers are familiar with this scenario: you launch a new version of an important web app, and the next morning your phone is ringing, and it's full of site problems.

As long as you are willing to admit that you may have made one or two mistakes, in which 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 revert to a previous version of the application and produce it. This gives you time to find out where the problem lies in the development environment when the production site is ready. This approach 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 changes made to the system.

One reason some developers dislike version control systems is because it adds a step to the development process, which means that the process of submitting code to the source control system and recovering the code through it is slowed down. This extra time to wait has hit some developers with patience.

5. Think that all projects require network services

Because of the over-propaganda of web services, many developers believe that Web services must be used in some form when developing projects. Although it may be necessary or appropriate to use Web services during the development process, it is not entirely possible. You need to analyze different situations to determine if it is appropriate to perform a network service. For example, another technique, such as remoting, may be more appropriate.

6. Ignoring the importance of confirming data

In the application code, the data is processed in a different form. For this reason, developers should confirm the integrity and validity of the data during the development process. This means that the data is read through a terminal database that can return 0 characters. The data is checked before execution, because the 0 value cannot be used in most operations.

