The terms that show up in quotes

A defined interface through which two programs talk to each other. Instead of exporting data by hand, one system fetches it directly from the other.

The part of an application nobody sees: database, domain logic, interfaces. This is where the actual work happens.

A copy kept separately from the original and tested regularly. A copy on the same drive is not a backup.

Automated steps that check and ship new code. They stop anyone from accidentally putting a broken version live.

Servers somebody else runs, paid for by usage. Convenient, as long as you know which data sits where.

Software built for one specific business, rather than bending a business around an off-the-shelf tool. Costlier up front, often cheaper to run.

Everything visible in the browser. Interface, interaction, and how it looks on different devices.

The European data protection regulation. It governs how personal data must be collected, stored and deleted.

The point where two systems exchange data. Usually also the point where projects take longer than planned.

Keeping dependencies current, applying security updates and making small adjustments. Without it even good software ages.

Continuous observation of a system. Good monitoring reports the fault before the first phone call.

The smallest version that is genuinely useful. Meant for learning early, not for leaving features out and charging full price anyway.

The versioned home of the source code. Every change is traceable and reversible.

Software as a Service: software you rent rather than buy, running at the provider.

A copy of the live system for testing. This is where you notice what still worked on the developer's machine.

Shortcuts in the code that save time today and charge interest later. Sometimes sensible, as long as you take them on knowingly.

A message one system sends another automatically as soon as something happens. The reverse direction of a classic query.