I've seen them go out of their way to pursue point-and-click solutions to data warehouses/lakes: thousands of ETL jobs manually coded (and manually tested) with very little "code" reuse. The inconsistencies/deviations from conventions were worse than the development waste. Consumers of these data will have to deal with inconsistencies in naming conventions, versioning strategies, and broken SCDs for years to come. Too often the architects/data modelers/ETL developers don't even know what the primary key is! (Don't lose your keys folks.)