Core jargon for software architecture, delivery, and engineering culture.
How much of the system — and how many users — would be affected if a given change or component fails.
A built-in constraint that prevents a system or user from taking an action known to be incorrect or unsafe.
Releasing a change to a small slice of users first and progressively widening it, rather than shipping to everyone at once.
Minimum Viable Product — the smallest version of a product that's still useful enough to release and learn from real users.
A single long-term metric or goal that smaller, day-to-day decisions are meant to align with.
A rough, throwaway build made to demonstrate that an idea is technically feasible — not to be shipped to production.
Request for Comments — a written design proposal circulated for team feedback before a risky or significant piece of work begins.
A short, time-boxed technical investigation done to answer a specific question or reduce uncertainty — not to produce shippable code.