This content originally appeared on DEV Community and was authored by Taslim Arif
Bad code haunts everyone sooner or later troubling the ones who wrote it along with the whole team.
Every developer in the world tries to write better and efficient code. I don't think that there is anyone who writes bad code deliberately.
Then why do we still get software and codes? Let's look at few reasons for bad code going to production which is generally termed as Technical Debts.
Think of a scenario where you took money from someone on interest, for that time being it solves your problem, right.
But eventually, you have to repay that money to a person with interest. Sometimes, we delay so much in repaying money that the amount of interest gets higher than the actual money which we took from a person which makes it impossible for us to repay the money.
The same is the case with software development, you write bad code, and keep on shipping it to production and since you were not focusing on improving the code, there will be a time when it becomes impossible for you to refactor/improve your code.
Reasons of technical debt
- Bussiness Pressure
Sometimes business pressure forces us to ship unfinished code to production. To make it work, we do some patches here and there and hides them. But this will come back haunting us.
Don't do this, it is okay to get delayed sometimes instead of shipping bad code to production because in a long time it will cost more money and effort to improve it.
- Developers not taking technical debts seriously or don't understand the importance of it
This is one of the most common cases, I have seen while working at various companies, many developers don't take these things seriously, for them working code is sufficient.
This becomes almost impossible to refactor and improve the code because your employer does not value it.
- Lack of Documentation
Documentation of one of the most important aspects of software development. It doesn't matter how good code have you written, if other developers can't understand, contribute or use it. We must write a good documentation explaining every aspect of your code so that others feel, it is easy to use and they don't need to ask you everytime.
- Incompetence
When the developer doesn’t know how to write decent code.
- Lack of knowledge sharing among team memebrs
When developers don't share their understanding of project with team mebers, it becomes lamost impossible for junior developers to work on it. They work in dark all the time and eventually create problems for themselve as well for whole team.
- Lack of tests
The lack of immediate feedback encourages quick, but risky workarounds or kludges. In worst cases, these changes are implemented and deployed right into the production without any prior testing. The consequences can be catastrophic. For example, an innocent-looking hotfix might send a weird test email to thousands of customers or even worse, flush or corrupt an entire database.
- Working in Isolation
This can lead to the accumulation of technical debt, which is then increased when changes are merged. The more changes made in isolation, the greater the total technical debt.
- Lack of compliance monitoring
This happens when everyone working on the project writes code as they see fit. There must a guideline to follow while writing, documenting, testing and deploying the code.
This content originally appeared on DEV Community and was authored by Taslim Arif
Taslim Arif | Sciencx (2021-09-26T11:35:57+00:00) Reasons behind bad Software code: Technical Debts. Retrieved from https://www.scien.cx/2021/09/26/reasons-behind-bad-software-code-technical-debts/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.