I used to work as part of a larger team in a fintech company before, and found db diagrams to be invaluable. I'd generate the db diagram for the small set of t

I used to work as part of a larger team in a fintech company before, and found db diagrams to be invaluable. I'd generate the db diagram for the small set of tables which my PR is touching, and highlight/annotate the changed columns/constraints (using ksnip) and attach it in the PR. It significantly reduced the back-and-forth between DBA/managers and sped up approval times. I have not found it useful to understand the table structure or domain model (which in our case could be very complex) but for explaining some scoped change/proposal to people who already had domain familiarity it proved to be very useful.