Here’s how your data retains its business relevance as it travels through your enterprise
I have previously written about the need to redefine the current data engineering discipline. I looked at it primarily from an organizational perspective and described what a data engineer should and should not take responsibility for.
The main argument was that business logic should be the concern of application engineers (developers) while all about data should be the data engineers’ concern. I advocated a redefinition of data engineering as “all about the movement, manipulation, and management of data”.
Now, as a matter of fact, the representation of application engineers‘ created logic actually also results in data. Depending on which angle we look at this from, it means that we either have a technical gap or too much overlap at the intersection of data and logic.
So let’s roll up our sleeves and commonly take on the responsibility for maintaining the dependency between logic and data.