> > Migrations first, not schema first. > ... TFA says this in the context of ORMs. But in the context of not-ORMs I think migration-first == schema-first: j

> > Migrations first, not schema first. > ... TFA says this in the context of ORMs. But in the context of not-ORMs I think migration-first == schema-first: just use `CREATE .. IF NOT EXISTS`, `ALTER ..`, etc. to set up the schema from the get-got, and you'll think about and cover migrations as you go. The problem with ORMs is that they hide the SQL bits and so if they don't get this right then you'll suffer.