Reverse ETL and Great Expectations

A lot of this logic has remained in these downstream tools because it is really easy for those downstream teams like marketing. To interact with an interface that ultimately produces some sort of logic without being super technical. There are two things that come to mind that I think are really helpful examples of patterns, and they're reverse ETL and great expectations. Reverse ETL is just an interface that allows that makes it easier to like interact with a database and then execute the result under the hood. Great expectations is interesting because it's the same concept between the other direction right. You define data definitions and great expectations but it automatically produces human readable documentation even though you're essentially using a Python library.