Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
What Is Unit Testing
Definition Unit testing is the practice of writing small, automated tests that check individual pieces of code — called units — in isolation. A unit is typically a single function or method that performs one specific task, such as calculating a discount or validating an email address. The test provides known inputs and checks that the output matches what is...
What Is Uptime
Definition Uptime is the percentage of time a website, server, or service is operational and accessible. It is typically expressed as a percentage over a given period — 99.9% uptime over a year, for example, means the service was unavailable for roughly eight hours and forty-five minutes across the entire year. Hosting providers and service-level agreements (SLAs) use uptime guarantees...
What Is a User Story
Definition A user story is a short description of a feature written from the user perspective: as a [role], I want [something], so that [benefit]. Why It Matters User stories keep development grounded in real needs rather than technical specifications. A feature that does not match how users work is wasted effort. Example Instead of build a date filter component,...
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 — and 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 actually 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 genuinely 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.