First, people think the term Debts as a terrible thing.
But it is NOT.
Debts is not bad if they are in control. It seems like the house loan nowadays. Borrowing money from banks makes you live in a better place. Better place or healthy environment gets your life easy and makes you feel better if you have steady financial income.
Technical debts of software development are similar as the commercial debts above. Technical debts occur if you want to obtain your predefined goal as soon as possible. Because you have not enough time or technical stack, you have to select ill-optimized solutions to solve programming problems.
Second, many programmers have contributed technical debts into the incoming deadline of software projects. They had to choose temporary solutions to meet the deadline at that time.
In fact, It is NOT.
It is your choice. It is your decision. These tech debts help you reach your goals as soon as possible.
In general, technical debts can be classified into five categories according to the phrase of software development.
- architecture and design.
- implementation with coding.
- software testing.
- document of software.
There is a standard procedure to avoid them.
- Use the pre-commit hook in the local computer to deal with the style of coding, Lint, UT.
- After Pull Request (PR), Continuous Integration (CI) does the pre-commit works again, and then do check the cover rate of codes and other tests.
- CI will fail if the rate of code coverage is becoming lower.
- PR can be merged after two code reviews.
Especially, software is changing dynamically like human organism. It is born, grows up, gets weak, and die at the end. We pay more attention to the technical debts of interface, rather than codes. We remove/refactor old codes easily, even rewrite codes.
- tech debts as a service.
- MVP is supper than tech debts.
- Hire the best.
- Vedor lock in.
[1] 陳天交胚，《技術(shù)債：the good, the bad, and the tao》份汗，2016.
(END)
