Spreadsheet until you need a database

A table is rows and columns. Each row is one thing you care about. Each column is one fact about that thing. A contact list with name, phone, and email is a table. A shopping list with item, store, and price is a table. You already use tables even when you do not call them that.

A key is the column that makes a row unique. In a contact list, an email address often works as a key if each person has only one. In a book catalog, a slug or ISBN can be the key. When two rows share the same key, your list lies. Fix that before you automate anything.

A spreadsheet is a table you can see and edit by hand. Excel, Google Sheets, LibreOffice Calc, and even a CSV file opened in a text editor all count. Spreadsheets win when the list is small, the edits are rare, and one person owns the file. They fail when three people edit at once, when you need the same fact in five places and keep typing it again, or when a formula quietly breaks and nobody notices for a month.

Use a spreadsheet first. Name the columns in plain language. Put one fact in each cell. Do not merge cells for decoration. Do not put two phone numbers in one cell with a slash between them. Split them into two columns or two rows. Future you will thank you when you try to sort or search.

Move to a database when you need rules the sheet will not keep for you. Examples: every order must point at a real customer, every book slug must be unique, every clean day count must belong to one profile. A database stores those rules. SQLite is a good first database on Windows. It is one file on disk. You can copy it. You can back it up. You do not need a server process running in the background.

Field Lattice on this house uses SQLite with full text search. The lesson for you is not the internals. The lesson is the shape: pages and chunks live in tables, a search index points at them, and the files on disk remain the masters you can open without the database. If the database file goes missing, you rebuild from the pages. That is honesty about storage.

Query literacy starts with one question: what do I want back? Select the columns you need. Filter the rows that match. Sort so the useful answer is on top. You do not need to memorize every keyword today. You need to refuse tools that hide the question behind a fog of frameworks until you can still say the question in English.

Backup means a second copy of the file, dated, somewhere you can find it. For SQLite, that is often as simple as copying the .db file to a dated folder. For a spreadsheet, copy the workbook before a big edit. Integrity means you can open the copy and see the same rows. Privacy means you notice when a table holds health notes, money amounts, or names of other people. Those rows need a smaller audience and a clearer reason to exist.

This lesson is not a database administration course. It will not make you a data engineer. It will help you decide when a sheet is enough and when a single file database is the next honest step. Finish it by doing one concrete job: take one real list you already keep, name its columns, pick a key, and write one sentence about whether it still belongs in a spreadsheet or needs SQLite.

Extra cuts

If you cannot say what makes a row unique, you do not have a table yet. You have a pile.

Cloud databases are optional. Name them when you choose them. Local file masters stay the default here.