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 P

140 terms

  • P-hacking

    P-hacking 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

  • P50 latency

    P50 latency is the serving concept concerned with p50 latency during AI inference.

    Inference performance

  • P95 latency

    P95 latency is the serving concept concerned with p95 latency during AI inference.

    Inference performance

  • P99 latency

    P99 latency is the serving concept concerned with p99 latency during AI inference.

    Inference performance

  • Paged attention

    Paged attention is the serving concept concerned with paged attention during AI inference.

    Inference performance

  • Paging policy

    Paging policy is the rules defining which conditions warrant immediate human notification.

    Reliability and observability

  • Pair programming

    Pair programming 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

  • Pair review

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

    Code review

  • Paired t-test

    Paired 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

  • Pairing time

    Pairing time is a developer productivity concept that helps teams understand pairing time in the context of software delivery.

    Developer productivity

  • Pairwise ranking

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

    Evaluations and benchmarks

  • Pairwise testing

    Pairwise 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

  • Pairwise win rate

    Pairwise win rate is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.

    Evaluations and benchmarks

  • Panel data

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

  • Parallel inheritance hierarchies

    A code smell in which adding one subtype in one hierarchy requires adding a matching subtype in another.

    Code quality and technical debt

  • Parameter count

    The number of arguments accepted by a function, method, or constructor.

    Code quality and technical debt

  • Pass at k

    Pass at k is the probability that at least one of k generated samples solves an evaluation task. It measures the benefit of giving a model several attempts, rather than the reliability of its first answer.

    Evaluations and benchmarks

  • Pass at one

    Pass at one is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.

    Evaluations and benchmarks

  • Pass-fail evaluation

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

    Evaluations and benchmarks

  • Paved road

    Paved road 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

  • Peer benchmark

    Peer benchmark is an analytical concept for using reference values to understand engineering performance, variation, or capability.

    Engineering analytics

  • Peer Group

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

    Engineering analytics

  • Peer mentoring

    Peer mentoring 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

  • Penetration testing

    Penetration 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

  • Per protocol analysis

    Per protocol analysis 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

  • Per-unit metric

    Per-unit metric expresses an amount relative to a defined unit of exposure.

    Engineering analytics

  • Percentage metric

    Percentage metric expresses a part-to-whole relationship out of one hundred.

    Engineering analytics

  • Percentile forecast

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

    Flow and capacity planning

  • Performance debt

    Performance 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

  • Performance testing

    Performance 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

  • Perplexity

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

    Evaluations and benchmarks

  • Pipeline as code

    Pipeline as code 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

  • Pipeline failure rate

    Pipeline failure rate 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

  • Pipeline flakiness

    Pipeline flakiness 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

  • Pipeline parallelism

    Pipeline parallelism is the serving concept concerned with pipeline parallelism during AI inference.

    Inference performance

  • Placebo effect

    Placebo effect 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

  • Plan accuracy

    Plan accuracy is a developer productivity concept that helps teams understand plan accuracy in the context of software delivery.

    Developer productivity

  • Planned capacity

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

    Flow and capacity planning

  • Planned work ratio

    Planned work ratio is a developer productivity concept that helps teams understand planned work ratio in the context of software delivery.

    Developer productivity

  • Planning cadence

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

    Flow and capacity planning

  • Planning horizon

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

    Flow and capacity planning

  • Planning interval

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

    Flow and capacity planning

  • Planning poker

    Planning poker 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

  • Platform adoption

    Platform adoption is the extent to which the intended software teams use an internal developer platform or one of its capabilities in their regular work. Adoption includes usage and continued use, but meaningful evaluation also asks whether the platform improves the outcomes it was built to support.

    Developer productivity

  • Platform engineering

    Platform engineering is the practice of building and operating internal platforms that give software teams self-service ways to provision, develop, test, deploy, and run applications. It treats the platform as a product for internal developers and aims to reduce unnecessary cognitive load.

    Developer productivity

  • Platform team

    Platform team 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

  • Point-based grading

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

    Evaluations and benchmarks

  • Poison message

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

    Reliability and observability

  • Policy as code

    Policy as code 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

  • Policy gradient

    Policy gradient 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