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 O

41 terms

  • Objective attainment

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

    Reliability and observability

  • Objectives and key results

    Objectives and key results 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

  • Observability

    Observability is the ability to understand a system's internal behavior from the evidence it produces. In software systems, that evidence often includes logs, metrics, and traces connected to enough context to investigate unexpected behavior.

    Reliability and observability

  • Observability dashboard

    Observability dashboard is a view combining metrics, logs, traces, and context for a system question.

    Reliability and observability

  • 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

  • Observability signal

    Observability signal is a recorded representation of system behavior that helps a team infer what is happening inside a service.

    Reliability and observability

  • Observational study

    Observational study 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

  • 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

  • Odds ratio

    Odds ratio 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

  • One-hot encoding

    One-hot encoding is a language-model concept about context selection and limits. 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

  • One-shot prompting

    One-shot 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

  • Open-closed principle

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

    Code quality and technical debt

  • OpenTelemetry

    OpenTelemetry is an open-source framework and specification set for generating, collecting, and exporting telemetry.

    Reliability and observability

  • OpenTelemetry Collector

    OpenTelemetry Collector is a vendor-neutral service that receives, processes, and exports telemetry.

    Reliability and observability

  • Operational capacity

    Operational capacity is the portion of a team's available capability used for support, incidents, maintenance, reliability, releases, and other work required to operate a service. It is part of real capacity even when it is not feature delivery.

    Flow and capacity planning

  • Operational definition

    Operational definition turns an abstract concept into repeatable observation rules.

    Engineering analytics

  • Operational readiness

    Operational readiness is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Operational toil

    Operational toil is recurring work needed to keep a service running that tends to be manual, tactical, automatable, and without lasting improvement. Its volume often grows with the service unless the underlying need is reduced.

    Reliability and observability

  • Opportunity scoring

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

    Flow and capacity planning

  • Order sensitivity

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

    Evaluations and benchmarks

  • Organizational Segment

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

    Engineering analytics

  • 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

  • OTLP

    OTLP is the OpenTelemetry Protocol for transmitting telemetry between instrumented systems, collectors, and backends.

    Reliability and observability

  • Outcome metric

    Outcome metric measures an effect on users, systems, or goals.

    Engineering analytics

  • Outcome orientation

    Outcome orientation is a developer productivity concept that helps teams understand outcome orientation in the context of software delivery.

    Developer productivity

  • Outcome-linked engineering

    Outcome-linked engineering is an approach that connects engineering decisions and delivery measures to the customer, product, business, or reliability outcomes they are intended to influence. It keeps software activity, system performance, and value evidence in the same decision context.

    Measurement and experimentation

  • Outcome-oriented roadmap

    Outcome-oriented roadmap 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

  • Outer loop efficiency

    Outer loop efficiency is a developer productivity concept that helps teams understand outer loop efficiency in the context of software delivery.

    Developer productivity

  • Output constraint

    Output constraint 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

  • Output context

    Output context 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

  • Output length

    Output length is the serving concept concerned with output length during AI inference.

    Inference performance

  • Output metric

    Output metric describes what a workflow immediately produced.

    Engineering analytics

  • Output quality

    Output quality is a developer productivity concept that helps teams understand output quality in the context of software delivery.

    Developer productivity

  • Output token

    An output token is a unit generated by a language model in its response. Output tokens include visible text and, depending on the API, structured fields or reasoning content returned for the application to process.

    Token costs and AI ROI

  • Output verbosity cost

    Output verbosity cost is expense associated with generating longer model responses. It gives teams a way to name, measure, or reason about an economic property of an AI workload without treating raw usage as proof of value.

    Token costs and AI ROI

  • Overfitting

    Overfitting is a language-model concept about evaluation design and failure analysis. It names a mechanism, representation, training practice, or operational behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • Overload control

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

    Reliability and observability

  • Ownership boundary

    Ownership boundary is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • 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

  • Ownership transfer

    Ownership transfer is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review