I agree for classes that are getting dropped, but for new classes you've just added I think it's unnecessary duplication. At the end of the day, migrations are meant to be transient and only run once to migrate an existing database and don't need to be re-runnable at some distant future point. If you're DB is that out of date or doesn't exist, then `schema:load` is the correct thing to use, not `db:migrate`.