In Data Engineering I only use DRY when it absolutely make sense. Code connecting to a database tends to be boiler plate, so can be abstracted away. However, I

In Data Engineering I only use DRY when it absolutely make sense. Code connecting to a database tends to be boiler plate, so can be abstracted away. However, I never abstract away ETL transformations, even if the code is duplicated. Often ETL logic starts out very repetitive in its early days, only to be customised further and further over the lifetime of the code. Each business stake holders tend to ask for modifications, e.g. can you please ignore sales in Australia for now, as it is handled by a different team, etc...