Some reasons to write a down method in your migrations

And it's probably not the reason you think.

Joel Clermont
Joel Clermont

Maybe you've always written down() methods in your migrations, and never gave it a second thought. Or maybe you're in the strict "anti-down()" camp and delete them from your migration stubs so you never even have to look at them.

In the latest episode of the No Compromises podcast, Aaron and I discuss why we write down() methods in our migrations, and it's probably not the reason you think.

Listen Now (14 min)

And after listening, don't forget to subscribe to the podcast so you don't miss future episodes.

Here to help,


P.S. Validation is really important in your app, but it doesn't always get the attention it deserves. We've written the ultimate guide to Laravel validation rules to help you get the most out of this powerful feature.

Toss a coin in the jar if you found this helpful.
Want a tip like this in your inbox every weekday? Sign up below 👇🏼

Level up your Laravel skills!

Each 2-minute email has real-world advice you can use.