I actually have previously written concerning the have to redefine the present data engineering discipline. I checked out it primarily from an organizational perspective and described what a knowledge engineer should and mustn’t take responsibility for.
The foremost argument was that business logic needs to be the priority of application engineers (developers) while all about data needs to be the information engineers’ concern. I advocated a redefinition of information engineering as “all concerning the movement, manipulation, and management of information”.
Now, as a matter of fact, the representation of application engineers‘ created logic actually also leads to data. Depending on which angle we have a look at this from, it implies that we either have a technical gap or an excessive amount of overlap on the intersection of information and logic.
So let’s roll up our sleeves and commonly tackle the responsibility for maintaining the dependency between logic and data.