When your "full stack" colleague puts his seeders in migration files.

A "fool" stacker?

"Run! You Full Stackers!"

Why is this bad (seriously, I need to know)? I used TypeORM once, and since it didn't have any seeding feature, so I had to check if the process was in a dev machine and insert the seeds during migrations.

I actually think it gives you more stability, since you are "simulating" several migrations on top of old data, since the data inserted in the preceding migrations you wrote will be transformed by the more recent migrations.

@bartmr in some cases (like this one) the seeding of the database, or to be more specific, creating model instances, can trigger events that want to write data to a table that not yet exists.

But actually the main reason for this post was ranting about developers calling themselves "full stack" but not knowing the basics of their frameworks ;)

@gmakkinga Yeah, that makes sense, specially in event driven services filled with multiple processes.