Very interesting article.
I love the “scratch your own itch” approach and I thought to build such a tool myself.
Thank you for the nearly objective post mortem (pros and cons).
This kind of problem is hard.
How to manage the migration of a storage (db, file hierarchy, stones piles)?
I wonder if we can mix both visions: ie writing the definition of the db schema at end, let the tool to write the migration files and allow developers to edit them (for data migrations, for customisation, for comments…) and possibly to resolve branches conflicts.
Again, I love this kind of articles: an issue, a personal view of a solution, an objective post mortem. Thank you