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 R

195 terms

  • Review wait

    Review wait is the queue portion of a change's review interval. It excludes the time spent actively reviewing when those boundaries can be identified.

    Flow and capacity planning

  • Review wait time

    Review wait time is the portion of a change's lifecycle spent waiting for a reviewer, response, or approval rather than receiving active feedback.

    Code review

  • Reviewable change

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

    Code review

  • Reviewer

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

    Code review

  • Reviewer assignment

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

    Code review

  • Reviewer availability

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

    Code review

  • Reviewer diversity

    Reviewer diversity is the range of technical perspectives, system familiarity, and lived experience represented in review decisions.

    Code review

  • Reviewer expertise

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

    Code review

  • Reviewer load

    Reviewer load is the amount and complexity of review work assigned to or completed by an individual or group.

    Code review

  • Reviewer rotation

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

    Code review

  • Reviewer specialization

    Reviewer specialization is the concentration of review responsibility in people with particular domain, security, or system expertise.

    Code review

  • Revision cycle

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

    Code review

  • Reward model

    Reward model is a language-model concept about mechanism and information flow. It names a mechanism, representation, training practice, or operational behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • Rework avoidance

    Rework avoidance is a developer productivity concept that helps teams understand rework avoidance in the context of software delivery.

    Developer productivity

  • Rework burden

    Rework burden is a developer productivity concept that helps teams understand rework burden in the context of software delivery.

    Developer productivity

  • Rework rate

    Rework rate is the proportion of work that must be repeated or revised because the earlier result was incomplete, incorrect, or no longer suitable. Its calculation depends on the work unit and the evidence used to identify rework.

    Code quality and technical debt

  • RICE scoring

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

    Flow and capacity planning

  • Risk-based testing

    Risk-based 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

  • Roadmap alignment

    Roadmap alignment 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

  • Roadmap capacity

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

    Flow and capacity planning

  • Roadmap planning

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

    Flow and capacity planning

  • Roll-forward

    Roll-forward 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

  • Rollback

    Rollback 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

  • Rollback frequency

    Rollback frequency 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

  • Rollback time

    Rollback time 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

  • Rolling average

    Rolling average smooths a moving window while retaining recency.

    Engineering analytics

  • Rolling deployment

    Rolling deployment 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

  • Rolling release

    Rolling release is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.

    DORA and DevOps

  • Rollout marker

    Rollout marker is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.

    DORA and DevOps

  • Root cause analysis

    Root cause analysis 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

  • Rotary positional embedding

    Rotary positional embedding is a language-model concept about mechanism and information flow. It names a mechanism, representation, training practice, or operational behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • ROUGE score

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

    Evaluations and benchmarks

  • Round-robin routing

    Round-robin 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

  • Route decision

    A route decision is the explicit selection of a model, provider, or execution path for an AI request. It should include the eligible options, the policy inputs, and the selected destination so the outcome can be inspected later.

    Model routing and gateways

  • Route explanation

    Route explanation is a model-routing or gateway concept used to manage operational visibility 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

  • Route reason code

    Route reason code 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

  • Route trace

    Route trace is a model-routing or gateway concept used to manage operational visibility 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

  • Routing audit log

    Routing audit log is a model-routing or gateway concept used to manage operational visibility 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

  • Routing configuration

    Routing configuration is a model-routing or gateway concept used to manage operational visibility 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

  • Routing metrics

    Routing metrics is a model-routing or gateway concept used to manage operational visibility 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

  • Routing policy version

    Routing policy version 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

  • Routing span

    Routing span is a model-routing or gateway concept used to manage operational visibility 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

  • Rubric-based evaluation

    Rubric-based evaluation is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.

    Evaluations and benchmarks

  • Rule suppression

    An explicit instruction that prevents a static-analysis rule from reporting a selected code location.

    Code quality and technical debt

  • Rule-based routing

    Rule-based 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