Schema

A schema is the blank form, not the answers you write on it. It's the shape your data has to fit, decided before any data shows up.

Picture a printed order form with labeled boxes, and each box is a specific shape. A round slot, a square slot, a slot that only takes numbers. The form is empty. It holds no orders yet. What it does is define what a valid order has to look like: this field is required, this one must be a number, this one is a simple yes or no. Try to jam a star-shaped answer into the round slot and the form bounces it right back. Wrong shape.

That's a schema: the agreed-on structure your data must follow. Which fields exist, what kind of thing each one is (text, number, date, true or false), which ones are required, which can be left blank.

Hold it next to the database, the giant spreadsheet that never chokes. A schema is that spreadsheet's column headers and the rules behind them. "Every customer row has an email, and it must be text. Every row has a signup date, and it must be a real date, not the word 'someday.'" The schema is the rulebook for the spreadsheet's shape. The data is what you pour into it.

Why this is worth a day: structure is what lets software trust its own data. If every order is guaranteed to have a real number in the "total" box, the code can add up a thousand totals without stopping to check each one for surprises. The schema is the promise that the shape holds. Break the promise, a missing field, words where a number belongs, and you get the bounce.

Where you'll hear it:

• "What's the schema for that?" means "what shape is that data? what fields, what types?"
• "We changed the schema" means "we changed the form itself," added a box, made one required. That's a bigger deal than changing one entry, because every existing record now has to match the new form.

And for the AI angle: when you want an AI to hand back data that another tool can swallow, you give it a schema first. "Answer in exactly this shape." That's how you stop it from writing a friendly paragraph when you needed a filled-in form.

The schema is the blank form. The data is the answers. Define the shape first, and everything downstream can trust it.