3 ms·

Am I understanding that you think that there should be just one data structure which is shared between all teams which is a superset of all fields that it could

Am I understanding that you think that there should be just one data structure which is shared between all teams which is a superset of all fields that it could have and people just add data to those fields? So at any given point you don't even know what data is present or not present depending on which point in the pipeline it has passed or not? At this point you may as well just use a object or dictionary. The type doesn't give you any idea about the actual shape of the data.

nerdchum 3y ago
Absolutely correct. > So at any given point you don't even know what data is present or not present depending on which point in the pipeline it has passed or not? At least with a non mutating data structure with the public contract you can tell if it's passed through a part of the pipeline because a required field is blank or null. With a mutating data structure that gets changed, say 20 different times throughout the system you have no idea if it's passed through some part of the pipeline or not. Even better if somehow everything can interact via a centralized database where all state is stored even intermediate state. Its not just storage. It's also state management.