No. 075·noun·also called dev environment, environments, dev/prod

Environment

A separate copy of the app, like development or production, each with its own settings and data.

SPECIMEN · DIAGRAM · COMPARE

Development

  • Fake data
  • Test keys
  • Break things freely

Staging

  • Copy of real setup
  • Final checks

Production

  • Real customers
  • Live keys
  • Handle with care
Definition

What it is

An environment is one running copy of your app. Most apps have at least two: development, where changes are made and tested with fake data, and production, the live app real customers use. Many add staging in between.

Environments keep experiments away from customers. Testing a "delete all" button in development is fine; in production it's a disaster.

Each environment usually has its own database and its own secret keys (test payment keys in development, live ones in production).

Say it like a builder

How to ask for it

Vague

“I don't want my testing to mess up the real customers.”

Precise

“Keep separate development and production environments: development uses its own database with seed data and Stripe test keys; production uses live keys. Never copy development data into production.”

Why it works

The weak prompt states a worry; naming environments and what differs between them (data and keys) is the actual safeguard.

In the wild

You've seen this in

  • SStripe's test mode vs live mode
  • AA "Preview" link before publishing
  • PSandbox accounts in payment tools
Usage note

Often confused with