A reference from Weave

Find a term

Understand the metrics, models, and methods behind modern engineering. Clear definitions, practical examples, and a closer look at what the numbers actually mean.

Terms beginning with T

155 terms

  • T-test

    T-test is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.

    Measurement and experimentation

  • Tail latency

    Tail latency is the serving concept concerned with tail latency during AI inference.

    Inference performance

  • Tail-based sampling

    Tail-based sampling is a sampling decision made after later spans and overall trace outcome are available.

    Reliability and observability

  • Target date

    Target date is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.

    Flow and capacity planning

  • Task batching

    Task batching is a developer productivity concept that helps teams understand task batching in the context of software delivery.

    Developer productivity

  • Task completion

    Task completion is a developer productivity concept that helps teams understand task completion in the context of software delivery.

    Developer productivity

  • Task completion rate

    Task completion rate is a developer productivity concept that helps teams understand task completion rate in the context of software delivery.

    Developer productivity

  • Task Decomposition

    Task Decomposition is a software-engineering concept describing how an AI coding system, its tools, or human collaborators handle a defined task.

    AI coding and agents

  • Task decomposition prompting

    Task decomposition prompting is a language-model concept about representation and similarity. It names a mechanism, representation, prompting pattern, decoding control, or context behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • Task difficulty

    Task difficulty is a developer productivity concept that helps teams understand task difficulty in the context of software delivery.

    Developer productivity

  • Task specification

    Task specification is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.

    Evaluations and benchmarks

  • Task switching

    Task switching is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.

    Developer productivity

  • Task type routing

    Task type routing is a model-routing or gateway concept used to manage traffic selection for AI requests. It describes a distinct decision, control, interface, or observation point between an application and one or more model providers.

    Model routing and gateways

  • Team capacity

    Team capacity is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.

    Flow and capacity planning

  • Team charter

    Team charter is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.

    Developer productivity

  • Team Comparison

    Team Comparison is an analytical concept for separating engineering observations into populations whose differences may matter to a decision.

    Engineering analytics

  • Team interaction mode

    Team interaction mode is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.

    Developer productivity

  • Team productivity

    Team productivity is a developer productivity concept that helps teams understand team productivity in the context of software delivery.

    Developer productivity

  • Team Topologies

    Team Topologies is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.

    Developer productivity

  • Team topology segment

    Team topology segment is an analytical concept for separating engineering observations into populations whose differences may matter to a decision.

    Engineering analytics

  • Technical debt

    Technical debt is the future cost created by technical choices that make software harder to change, operate, or understand. The debt metaphor distinguishes the work needed to improve the design from the recurring friction of leaving it as it is.

    Code quality and technical debt

  • Technical debt prioritization

    The practice of ordering debt work using impact, urgency, effort, and evidence.

    Code quality and technical debt

  • Technical debt ratio

    A ratio that compares estimated remediation cost with the cost or value of the related software asset or scope.

    Code quality and technical debt

  • Technical debt register

    A maintained list of known technical debt items with context, impact, ownership, and next action.

    Code quality and technical debt

  • Technical debt remediation

    Work that reduces the cost, risk, or constraint created by a previous technical tradeoff.

    Code quality and technical debt

  • Telemetry

    Telemetry collects and transmits observations about systems and workflows.

    Engineering analytics

  • Telemetry cost

    Telemetry cost is the compute, network, storage, query, and operational expense of observability data.

    Reliability and observability

  • Telemetry pipeline

    Telemetry pipeline moves observations through collection, processing, storage, and presentation.

    Engineering analytics

  • Telemetry signal

    Telemetry signal is a distinct form of machine-generated evidence such as a metric, log, trace, or profile.

    Reliability and observability

  • Tell-don’t-ask

    A design guideline that favors asking an object to perform behavior instead of extracting its state to decide elsewhere.

    Code quality and technical debt

  • Temperature

    Temperature is a generation parameter that changes how a language model samples from the probability distribution of possible next tokens. Higher values generally allow more variation, while lower values generally favor higher-probability choices.

    LLM fundamentals

  • Temperature scaling

    Temperature scaling is a language-model concept about instruction design and control. It names a mechanism, representation, prompting pattern, decoding control, or context behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • Temporary fix

    Temporary fix 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

  • Tenant isolation

    Tenant isolation is a model-routing or gateway concept used to manage policy enforcement for AI requests. It describes a distinct decision, control, interface, or observation point between an application and one or more model providers.

    Model routing and gateways

  • Tenant routing

    Tenant routing is a model-routing or gateway concept used to manage policy enforcement for AI requests. It describes a distinct decision, control, interface, or observation point between an application and one or more model providers.

    Model routing and gateways

  • Tensor fusion

    Tensor fusion is the serving concept concerned with tensor fusion during AI inference.

    Inference performance

  • Tensor parallelism

    Tensor parallelism is the serving concept concerned with tensor parallelism during AI inference.

    Inference performance

  • Termination drain

    Termination drain is a reliability concept used to describe a specific condition, control, or decision in the operation of software services.

    Reliability and observability

  • Test automation

    Test automation 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

  • Test automation framework

    Test automation framework 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

  • Test case

    Test case 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

  • Test charter

    Test charter 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

  • Test coverage

    Test coverage measures which parts of a program or its behavior are exercised by a set of tests. Code coverage commonly reports executed lines, statements, branches, or functions, while other coverage measures track requirements or scenarios.

    Code quality and technical debt

  • Test data

    Test data 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

  • Test data management

    Test data management 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

  • Test debt

    Test 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

  • Test determinism

    Test determinism 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

  • Test duration

    Test duration 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

  • Test environment

    Test environment 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

  • Test execution

    Test execution 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