1. It is considered that you must use Visual Studio.net to develop .NET applications
Those who have not known to Microsoft .NET have thought that Visual Studio.NET must be used when developing applications using .NET Framework. This is not correct. You only need to install the .NET framework that you can download for free on your Microsoft website.
Install the .NET framework, you can develop your favorite text editor and .Net tool command line for development. Moreover, you can also apply third-party development tools, such as SharpDevelop.
For discussion about Visual Studio.Net, see the previous column. The choice of development tools varies from person to person, but many development teams are standardized to simplify work.
2. Exclusive information
One of the significant features of the developers will tend to Tight Tight. The ability that is not unknown, often causing a sense of excellence. Conversely, sharing information helps team expansion knowledge. In addition, with the addition of other team members, sharing information can also be improved. Finally, when you explain an idea or idea to another or a group of developers, your knowledge is expanded.
Teamwork spirit is the driving force of Agile Software Developments. In addition, many teams use the peer code reviews, the developer reviews and comments on other developers, which promotes the learning and understanding of both parties.
3. Ignore the code comment
Add a simple and straightforward approach to your code, but why everyone always ignores this? Some developers mistakenly believe that the reduction of document certificates (any form) can improve work safety. This is a fallacy like the exclusive information discussed earlier.
A small amount of reasonable arrangements can greatly improve the readability of the code and facilitate the management of the code. There is now a trend of too much annotation. Basically, these annotations should be a brief description of code, variables, methods, etc. Many teams like to insert comments when modifying the code. When (if) occurs, we are easy to find out what modifications have been previously done.
4. Didn't see the value of the version control system
Most developers are very familiar with this situation: you launch a new version of an important network application, the next morning, your phone is not stopped, and it is full of website problems.
As long as you want to admit that you may have made one or two mistakes, the version control system in this case 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 and production. This allows you to find out the problem in the development environment in the development environment in the production location. This approach is much more advantageous than finding a problem by searching 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 don't like the version control system is because it adds a step to the development process, which means that the code is submitted to the source control system and slow down by it to recover the code. This extra wait time hits some of the patient's patience.
5. We believe that all projects need network services
Due to the over-propaganda of network services, many developers believe that the network service must be used in some form when developing projects. Although it may be necessary or appropriate in the development process, it is not entirely possible. You need to analyze different situations to decide whether to perform network services properly. For example, another technique such as Remoting may be more appropriate.
6. Ignore the importance of confirming data
In the application code, the data is processed in different forms. For this reason, developers should confirm the integrity and effectiveness of the data during the development process. That is to say, data should be read by the terminal database that can return zero characters. Check the data before execution, because the zero value cannot be used in most operations. Learn more than half of success
Whether you are a newcomer or older, you have to realize the trend of developers to make this six mistakes. Even if you find yourself without these bad habits, you have to realize that other developers in your team may make these mistakes. These potential errors are kept vigilant so that these errors prevent these mistakes from planning your team.
