A reference from Weave

Find a term

Understand maintainability, code structure, and the costs of decisions that make future changes harder. Learn what quality signals can and cannot establish.

Terms beginning with O

6 terms

  • Observability debt

    Observability debt is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt

  • Obsolete code

    Obsolete code is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt

  • Open-closed principle

    A design principle that favors extending behavior through stable contracts rather than repeatedly modifying trusted code.

    Code quality and technical debt

  • Orphan abstraction

    An abstraction that has no clear owner, consumer, or responsibility in the current design.

    Code quality and technical debt

  • Orphaned code

    Orphaned code is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt

  • Ownership debt

    Ownership debt is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt