The one problem this technique has is that data and software normally have two very different speed and correctness requirements. That means that data and software should evolve following different procedures, what heavily implies that you want different people working at them, or at least you want people to look at them at different times.

For that, you really want independent access controls and CI tooling.

Of course, you can't separate much if you are a 1 or 2 people team at early stages of some project. And it may help you move faster.

But:

> "Rebuilding the database is as simple as executing one line bash loop (I do it every few minutes)"

This denounces a very development-centric worldview where operations and maintenance don't even appear. You can never rebuild a database, and starting with the delusion that you will harm you on the future.