Happened-Upon Technical Debt | Glossary

 

Definition

The form of Technical Debt , whose existence is unaware to the software team unless it is revealed, or exposed during the usual course of development, is known as Happened-Upon Technical Debt.

Further Reading

For more on Happened-Upon Technical Debt, read here.

Naive Technical Debt | Glossary

 

Definition

Technical Debt is the extra cost incurred during development period, when a short and quick solution is used, instead of a safer one that would take more time. Naive Technical Debt  occurs where a specific best practice is not followed due to junior level developers being unaware of the best design pattern, documentation or guidelines.

Further Reading

  • Refactoring for Software Design Smells: Managing Technical Debt”(book), by Girish Suryanarayana.
  • For more on Known Technical Debt, read here,