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

  • Retrieval evaluation

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

    Evaluations and benchmarks

  • Retrospective action

    Retrospective action 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

  • Retry amplification

    Retry amplification is the serving concept concerned with retry amplification during AI inference.

    Inference performance

  • Retry budget

    Retry budget is a model-routing or gateway concept used to manage reliable request governance 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

  • Retry policy

    Retry policy is a model-routing or gateway concept used to manage reliable request governance 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

  • Retryable error

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

    Reliability and observability

  • Revert review

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

    Code review

  • Review abandonment

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

    Code review

  • Review backlog

    A code review backlog is the accumulated set of proposed changes that still require review activity or a final decision.

    Code review

  • Review bottleneck

    A review bottleneck is a constrained person, team, policy, or stage that limits the movement of proposed changes.

    Code review

  • Review capacity

    Review capacity is the effective ability of reviewers to assess eligible changes during a period. It depends on change scope, reviewer context, specialist requirements, interruptions, and the standard of review expected.

    Flow and capacity planning

  • Review capacity buffer

    A review capacity buffer is deliberately uncommitted reviewer capacity reserved for incoming changes, urgent work, and variation in review difficulty.

    Code review

  • Review capacity planning

    Review capacity planning is the practice of matching expected code review demand with the people, ownership, time, and knowledge needed to provide timely and effective review. It treats review as a delivery capability rather than spare work performed after implementation.

    Developer productivity

  • Review comment

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

    Code review

  • Review comment density

    Review comment density is the number of review comments relative to a chosen unit such as changed lines, files, or pull requests.

    Code review

  • Review comment resolution

    Review comment resolution tracks whether feedback receives a response, code change, explicit rationale, or documented decision.

    Code review

  • Review coverage

    Review coverage describes the share of eligible changes that receive the intended review evidence before integration.

    Code review

  • Review cycle count

    Review cycle count is the number of meaningful feedback and revision cycles a change passes through before its review is complete.

    Code review

  • Review defect detection

    Review defect detection is the practice of finding correctness, security, reliability, or maintainability problems before code reaches later stages.

    Code review

  • Review depth

    Review depth describes how carefully a change is examined across behavior, design, tests, security, and maintainability.

    Code review

  • Review effectiveness

    Review effectiveness is the extent to which a review finds useful problems, improves shared understanding, and supports a safe change.

    Code review

  • Review finding rate

    Review finding rate is the frequency at which a review identifies a defined issue class before a change is integrated.

    Code review

  • Review handoff

    A code review handoff transfers responsibility for understanding and progressing a proposed change from one reviewer or team to another.

    Code review

  • Review iteration

    A review iteration is one cycle of author changes followed by reviewer feedback on the same proposed change.

    Code review

  • Review iteration count

    Review iteration count is a developer productivity concept that helps teams understand review iteration count in the context of software delivery.

    Developer productivity

  • Review load distribution

    Review load distribution shows how review requests or completed reviews are spread across people, teams, repositories, or change types.

    Code review

  • Review meeting

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

    Code review

  • Review noise

    Review noise is feedback or workflow activity that consumes attention without helping a reviewer or author make a safer, clearer change.

    Code review

  • Review objective

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

    Code review

  • Review participation

    Review participation is a developer productivity concept that helps teams understand review participation in the context of software delivery.

    Developer productivity

  • Review plan

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

    Code review

  • Review priority

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

    Code review

  • Review quality

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

    Developer productivity

  • Review queue

    A review queue is unfinished change work awaiting review activity or a review decision. Its depth and age reveal demand on reviewers and the delay between implementation and the next delivery step.

    Flow and capacity planning

  • Review queue age

    Review queue age is the time that pending review work has remained without the next required action.

    Code review

  • Review queue depth

    Review queue depth measures the number of pending review items at a point in time or across a defined workflow stage.

    Code review

  • Review queue pressure

    Review queue pressure is the condition in which pending review work consumes more capacity than the responsible reviewers can sustainably provide.

    Code review

  • Review rejection

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

    Code review

  • Review rejection rate

    Review rejection rate is the share of submitted changes that are declined, abandoned, or sent back rather than accepted in their current form.

    Code review

  • Review reopen rate

    Review reopen rate is the share of closed review requests that become active again for additional changes or decisions.

    Code review

  • Review request

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

    Code review

  • Review response time

    Review response time measures how long a reviewer or author takes to respond to the next actionable event in a review conversation.

    Code review

  • Review responsiveness

    Review responsiveness is a developer productivity concept that helps teams understand review responsiveness in the context of software delivery.

    Developer productivity

  • Review rework

    Review rework is the author effort or change volume produced in response to review feedback before a proposed change is accepted.

    Code review

  • Review scope

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

    Code review

  • Review service level expectation

    A review service level expectation is a probabilistic statement about how long a defined class of review requests usually takes.

    Code review

  • Review signal-to-noise ratio

    Review signal-to-noise ratio compares useful, actionable review feedback with comments that are irrelevant, duplicated, or purely cosmetic.

    Code review

  • Review SLE

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

    Code review

  • Review state

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

    Code review

  • Review turnaround time

    Review turnaround time is the elapsed duration from a review request to a defined completion point, such as approval or final feedback.

    Code review