[carterschonwald]

This thread comes at a fortuitous time: I’m exploring a product idea around making a toolkit for reasoning about how schemas and tables are inter related across an organizations database systems.

The near term is to make it easier for organizations to maintain the various gdpr style mandated user data export and deletion capabilities without it getting in the way of / blocked by continuously evolving software systems efforts.

The same sort of tooling could also be used to help data analysis folks navigate the huge sea of tables in various datalake setups organizations are so eager to setup (it can be tricky seeeing which things are usefully joinable among many many evolving datasets that might be in that setting.

This of course isn’t really aimed at solo engineer sized application Systems such as the original poster, but is it something folks would find useful?