Glossary

The words this site uses, in plain English

Most of the vocabulary here is ordinary in software engineering and unfamiliar outside it. These are the definitions, written for a reader who does not build software for a living.

CI/CD
Continuous integration and continuous delivery. The practice of checking every change automatically, and of shipping it automatically once the checks pass.
Runner
The machine that runs your checks. Usually rented by the minute, and shared between everyone on the team.
Pipeline
The sequence of steps a change goes through: check, build, test, deploy.
Local-first
Designing a tool so the work happens on your own machine first, and only goes to a shared machine if it genuinely needs to.
Air-gapped
A system that never talks to the internet. Some banks and governments require this, so their tooling has to work without any external service.
Deterministic
Giving the same result every time. If a check passes on your laptop and fails on the server, something is not deterministic.
Toolchain pinning
Recording the exact versions of the tools a project uses, so every machine uses the same ones.
Build gate
A check that runs on every build and fails it if something has gone wrong — so the problem is caught before it ships.
Footprint
How much memory and CPU something uses while it is running. A small footprint means it can run on a laptop instead of a server.
Idle CPU
The processing power a program uses while it is doing nothing. A mock that burns CPU while waiting is a program that heats up your laptop.
Dependency
Someone else's code that your project depends on. Every dependency is also a thing you have to install, check and keep up to date.
Zero-dependency
A project with no outside code at all, built only on what the language already provides.
Mock
A stand-in for a real service, so a test can run without the real service, an account, or a network connection.
Blueprint
A structured file that describes a workflow, rather than code that performs one. It can be read and reviewed by a non-programmer.
Plugin
A file dropped into a folder to add a capability. The program finds it by itself — no registration, no edit to the main code.
Runspace pool
A set of workers that lets a program handle many things at once without one slow job blocking everything else.
Thread-safe
Safe to use from several workers at the same time without the workers corrupting each other's data.
Webhook
One service calling another to say something has happened. Used by payment providers to tell you a payment went through.
OpenAPI
A published description of what a service accepts and returns, so a stand-in can be built from the same contract the real service uses.
RBAC
Role-based access control. Different people get different permissions — some can look, some can act, some can change the rules.
Audit trail
A record of what happened, kept as it happens, rather than reconstructed afterwards from logs.
Exponential backoff
When something fails, wait twice as long before trying again. Two seconds, then four, then eight — so a struggling service is not hammered.
Idempotent
Safe to run twice. Doing the same thing again does not do it again — which is what stops a failed retry from charging a customer twice.
Observability
Being able to see what a system is doing from the outside, without changing it.
Blue-green deployment
Releasing by running the old and the new version side by side and switching traffic over, so a bad release is switched back instantly.