Developers are doing mistakes often due to the lack of making scenarios. In my personal experience, I have faced some common issues. Also, as a team manager, I have faced a few common mistakes made by the developers during their development period. This will helpful for the developers who are being right now in the IT field to increase their credibility.
While comparing the two string values, it is mandatory to convert both the values into lowercase. It must be followed in any language programming. If we failed to do that, due to the casing issues, the scenario getting failed here.
While working on UI, it is mandatory to ensure the alignment in most used browsers. Some of the CSS properties cannot be supported by the old IE browsers,
display: grid, table
Nowadays, most of the websites are supporting the responsiveness based on the device screen resolutions. So, it is always mandatory to make the compatibility for all the resolutions by the developers. We should not avoid any screen resolutions during the development period. The common resolutions to be considered for responsiveness are as below,
- smaller than or equal to 768 px (smartphones)
- larger than 768 px (small devices, tablets)
- larger than 992 px (medium devices)
- larger than 1200px (large devices)
It is mandatory to make sure the recursive loops have ended at a certain limit. If failed, this could be the cause for the server hang issues due to high CPU usage and hence the page went not reachable.
Since the multi-thread programs are running parallel to each other, the values for the next consecutive threads should not depend on the previous threads. The developer should make sure during the development period itself.
It cannot be predicted when the database has a minimum quantity of data. The issue may occur when the database reached a larger quantity of data.
We should always validate the user’s input based on the criteria that we have defined in client-side as well as server-side. It is not enough to be handled the validation on the client-side alone. The validation condition should be the same to be handled in both sides. We should not trust the user’s input.
The developer must take the responsibility to do the developer side testing. During testing, the developer must test the validation part with various inputs for all the inputs especially for email or domain name fields if any.
It is mandatory for the developers to handle the exception and do the alternate message/functionality to be done in the catch section. It should be followed by all the language developers. We have to expect the possible exceptions and need to handle all those exceptions in the development period itself.
Avoid using the hardcoded values in the development code. Instead, you can have the hardcoded values in the .config files and make use of it wherever you would like to use it. It will be useful if we need to configure another value in the production/development servers after deployment.
The above are the common mistakes made by the developers in real-time in their career. Also, it can be considered as a best practice for the developers.
Find more interesting blogs to read here,