A reference from Weave

Engineering & AI glossary

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

All terms

2,008 terms

  • Workload balance

    Workload balance is a developer productivity concept that helps teams understand workload balance in the context of software delivery.

    Developer productivity

  • Workspace routing

    Workspace 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

  • Written communication

    Written communication 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

  • WSJF

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

    Flow and capacity planning

  • Z score

    Z score 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

  • Zero-downtime deployment

    Zero-downtime deployment is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.

    DORA and DevOps

  • Zero-shot prompting

    Zero-shot prompting 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

  • Zombie code

    Zombie 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