Rails schema not updating validating microsoft office
I can create simple objects and compose them in ways that Rails does not explicitly endorse!
A few examples of real world seed migrations: Applying those migrations will automatically update the seeds file with instructions to recreate all the objects.
Most will add utility modules with class-methods in lib/, but that's it.
It takes 2-3 years before developers realize: "Rails is just Ruby.
Furthermore, this is not business logic and thus should not stay forever in the code base.
A second issue is that those data migrations might be ignored by future developers if instead of running file without touching the migrations.