When building a data warehouse for a product, business people usually need some kind of daily log on a level of a single entity (so, you want to know what the customer data looked like on a day x). This is a rather regular task for a data engineer. It’s also not the most challenging one.

But sometimes there’s a database imp upstream. It tells database developers not to put update timestamps in tables. It convinces them changelogs are stupid and not worth investing a bit of resources. It suggest them to put data from different contexts (and systems) into one table, without traceability and lineage.

Guys, the imp’s wrong, don’t listen to him. And let me know if you’ve heard his sweet but wrong voice, so we could battle him together.