7 Common Mistakes Web Developers Make
Ignoring production errors
Programmers write automated tests and follow the TDD technique to make sure the code doesn’t crash. Only this is done on the sendbox, and we often forget about tracking bugs / bugs on already running projects.
To track JS errors you can use:
Making changes directly on the server
Such changes are likely to be lost with the next update. And so then there is a double job – writing the same code a second time.
Downtime during deployment
When deploying code on a server, in most cases the site is disabled. Obviously, this is bad from any point of view.
Therefore, it is always recommended to use deployment policies that roll the code onto the server without stopping it.
Developers always keep secret credentials, API keys, user information, and so on in the code itself. If this is a client-side code, you risk a lot.
Having a backup is the same as having insurance. If the change made to the server “laid” it, and you do not have backups – there will be big problems. You will have to consistently roll all versions to return to normal. This will require more time and nerves than rolling back to the control point.
No one wants to wait for the site to load. Therefore, caching is one of the main tools that should be used in development.
Manual deployment takes a lot of time, is complicated and often causes big problems. A couple of unintended clicks made by an inexperienced developer, and – voila! – all work has disappeared.