>then use database migrations (e.g. with alembic) +1 for Alembic, it makes database schema changes a lot less painful. It's definitely good to sit down and fig

>then use database migrations (e.g. with alembic) +1 for Alembic, it makes database schema changes a lot less painful. It's definitely good to sit down and figure out high level architecture before building, but for small one-off projects code that works today is usually worth more than better code tomorrow.