Great article. I can't imagine a real world scenario where I'd ever use a down migration in production. Even if you completely botch a migration, the next step is to write a new migration to correct the situation! "Rolling back" a commit is not even logically possible; the database schema history only moves forward.