Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
Package Manager
What It Actually Means A package manager installs, updates and keeps track of the third-party components a project uses. npm for JavaScript, Composer for PHP, pip for Python. A developer states which packages the project needs, and the tool fetches them and everything they in turn depend on. The Two Files That Matter Every package manager produces two, and the...
Penetration Testing
What It Actually Means A penetration test is a skilled person deliberately attempting to break into your system, with permission, and then telling you how they did it. The distinguishing feature is the human. A tester chains small weaknesses into a real attack in a way automated tools cannot: a version number here, a permissive setting there, an error message...
PPC (Pay-Per-Click)
What It Actually Means Pay-per-click means paying only when somebody clicks your ad. You bid on search terms, your ad appears among the results, and you are charged per click rather than per appearance. Its defining property is speed. Organic search takes months. A paid campaign can be producing enquiries the same afternoon, which makes it the fastest available way...
Production Environment
What It Actually Means Production is the live system: the one customers use, holding real data, taking real money. Everything else, development machines, staging, test environments, exists so that production can be changed safely. It is the only one where mistakes have consequences, and the discipline around it is what separates a well-run system from a risky one. The Rules...
Progressive Web App
What It Actually Means A progressive web app is a website built so it can be installed on a phone, appear as an icon, run without a browser bar, work offline, and receive notifications. It is not a separate product. It is your existing web application with a few additional capabilities that browsers now support. Why It Matters Commercially The...
Prompt Engineering
What It Actually Means Prompt engineering is writing the instruction given to a model so that it produces what you actually want. The effect is real and larger than people expect. The same request phrased two ways can produce a usable answer and a useless one, because the model is responding to everything in the input, including what you did...
Pull Request
What It Actually Means A pull request proposes a set of changes to be merged into the main codebase, and holds them open for review first. GitLab calls the same thing a merge request. Practically it is a gate. Work happens separately, it is proposed, something checks it, someone approves it, and only then does it become part of the...
About the Glossary
Why Plain Language Matters More Than Technical Fluency
Every software project involves terminology that business owners are expected to understand but rarely have reason to learn. Developers use terms like API, CI/CD, middleware, and bearer token as if everyone shares the same vocabulary. When a client nods along without fully understanding, decisions get made on incomplete information. That gap between technical language and business understanding is where the most expensive mistakes happen: approving architectures you cannot evaluate, signing off on testing strategies you cannot verify, and accepting timelines based on concepts you have not had properly explained.
This glossary exists to close that gap. Each entry provides a plain-English definition, an explanation of why the term matters to your business, and a concrete example of the concept in action. These are not textbook definitions written for computer science students. They are practical explanations for the person who needs to make decisions about software without becoming a developer in the process.
We built this glossary from the questions our clients ask in discovery calls, during project reviews, and in Slack threads where someone finally admits they are not sure what a term means. The entries reflect what business owners need to understand, not what a technical writer thinks is important. Across hundreds of client engagements, we have found that the single biggest predictor of a smooth project is a client who understands enough vocabulary to ask the right questions. Not to write the code. Just to evaluate the answers they are given.
The definitions here deliberately link to deeper content elsewhere on the site. If a glossary entry sparks a question about how we implement something, the Knowledge Center, Services, and Systems sections have the full picture. The glossary is the starting point, not the destination.
Need a Term Explained?
If you have come across a term we have not covered yet, let us know and we will add it.