10 Mistakes Every Internet Developer Would Regret
Admit it! We all make mistakes. None of our codes start working on the first hit. We make typos, forget to log out, or, like most of us, overlook the testing phase, especially when it comes to ASP.net development. To err is human. So making mistakes is just another human phenomenon. It’s how you address your mistakes and how you come up with ways to avoid them in future projects that counts. Here is a compilation of some of the most common testing mistakes that developers often make while servicing .Net development needs. We’ll see.
XSS security issues: The appearance of your user interface and, of course, its maintenance is in your hands. Make sure all user input fields are well-customized so that any JavaScript or HTML a user enters can’t poke around your web page.
universal location: As a rule of thumb, when you start developing a new feature, you keep all text hard-coded, as certain changes are likely to occur during the course of development. As soon as the project team approves the feature, they localize the text. However, sometimes you tend to forget the locations of all the text. It remembers to code, but when it comes to localization, it tends to log out without doing the same. This checklist probably reminds us to locate ourselves before logging out next time.
.Net behaves well with IE 6 and 7 and Firefox: Test drivers often report cross-browser compatibility issues that crop up from time to time. Most of these issues tend to cover small branches like the usual IE 6 issues or minor issues related to element positioning. We are focusing exclusively on versions 6 and 7 of IE and Mozilla Firefox for two reasons. First of all, if your web page works well in these three browsers, it will also work well in Opera and Safari. Second, more than 98% of visitors access your site through these browsers.
Reuse code when necessary: This law applies to all programming platforms, and ASP.Net is no exception. Separate server and user control elements allow for specialization of the code so that it can be used elsewhere as well.
Commenting on the Code: There are no two ways to this. Always document your code well, and comment in the right places, to make it easier for other developers to pick up where you left off.
Stretched text does not mean broken layout: In fact, names usually don’t extend beyond 50 characters, but what happens if some user enters a name that contains 300 or even more characters? Obviously, in that case, the user interface will be broken. In this case, you have two options: either code your interface to accept long text input, or put a limit on the length of text that users can enter.
Write units when possible: Unit testing for your website can be a tedious job, especially if you are not using the ASP.Net MVC framework for the same. However, extracting the code-behind logic into different components that can be placed in the library can allow you to unit test. Instead of dealing with HttpHandlers using .ashx files, putting them in separate libraries is a good option.
Peer verification before testing: Before you sign off on any newly added features and submit them to the testing team, you typically pass them through peer verification. As the name suggests, in peer verification, one of your colleagues tests the application feature that he has just developed and tries to find fault with it. This allows you to easily identify bugs and also simplifies the process for the test team. When schedules are really tight, we often forget to ask for peer verification and it definitely shows last.
Expected behavior of the Enter key: When you use web forms in ASP.Net, the Enter key often starts acting strangely. In this case, you can set the default buttons in the Panel web control or from code behind.
Sign for Product Owner: By default, ownership of a product feature rests with the product team. Developers also have an ownership stake, but that’s only down to the implementation level. Often when you have too much to handle, you forget to get an endorsement from the product owner. If the owner doesn’t sign your work, it means you haven’t completed it, even if you’ve already marked it as done. This is frustrating and can extend deadlines.
The aforementioned mistakes are common and can be made by any developer. If you are an Asp.net developer, these bugs should be fixed in the next development company. If you are a business owner looking to hire .net developers, then make sure your developers take care of the same while developing your web application.