I learned my first SQL queries on a tiny practice database I built myself, and I still think that was the right way. A lot of what pushed me forward came from reading pieces on Database Secrets, where people explain how queries behave instead of just listing syntax. My database had three tables and barely any rows, which was perfect.

The first thing I understood, slowly, was that reading comes before writing. SELECT before INSERT, UPDATE or DELETE. I spent a whole evening pulling columns out of one table, renaming things with aliases, watching what came back. Boring? A little. But when I finally typed an update without a where clause and wiped every row, I already knew how to check what I had done, and I reloaded the file and started over.

Filters came next. I stacked conditions with AND and OR, mixed them badly, got nonsense back, and only understood why when someone pointed out that SQL honors parentheses before anything else. That was the day I learned it does what you tell it, not what you meant.

Joining two tables took me longer. I had a table of books and a table of authors, and I wanted a list with author names next to the titles. My first attempt returned a mess where every book appeared beside every author, because I had forgotten the condition linking the two. Once it worked, something clicked. A join is just a match between two columns, nothing magical about it.

Errors used to annoy me. Now I read them. A missing comma, a stray quote, a column that does not exist: each message points at something specific, and after a while you start to recognize the shapes. I keep a file of queries I got wrong, with a note on what was broken. The same mistakes come back.