Technical Debt
5 Tips To Keep Technical Debt Under Control Debt
Debts#
- The supermarket handcart unlocking coin is a good example of a technical debt.
- Deliberate Technical Debt: On starting up: fast cheap code; select of library.
- Accidental / Outdated design: Need for functionality, market(objective, requirements) chang. Some bad design would need huge refactor when they change.
- Bit Rot: codes are changing bit by bit and someone may change the code and break or wrapping too many layers.
Control Debts#
- Write Design Docs. Easier to refactor outdated design. [Google design docs]#LINK
- Code review, code standard: For bit rot.
- Make it explicit: Write technical debts in back log (currently JIRA).
- Leave room for debt: Some space in every Sprint to fix some debt.
- Prioritize.
- Introduce metrics.