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 L

7 terms

  • Lack of cohesion

    A family of measures that estimates how weakly the responsibilities or data uses within a class are connected.

    Code quality and technical debt

  • Law of Demeter

    A guideline that limits how many unrelated object relationships a method navigates directly.

    Code quality and technical debt

  • Legacy modernization

    Legacy modernization 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

  • Legacy system

    Legacy system 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

  • Liskov substitution principle

    A design principle that requires a subtype to remain valid wherever its declared base type is expected.

    Code quality and technical debt

  • Load testing

    Load testing is a software testing or test-design practice used to gather evidence about a defined risk, behavior, boundary, or operating condition. It makes the question under test explicit, identifies the inputs and observations that matter, and gives a team a repeatable basis for deciding whether the result is acceptable.

    Code quality and technical debt

  • Localization testing

    Localization testing is a software testing or test-design practice used to gather evidence about a defined risk, behavior, boundary, or operating condition. It makes the question under test explicit, identifies the inputs and observations that matter, and gives a team a repeatable basis for deciding whether the result is acceptable.

    Code quality and technical debt