I love the hierarchy of needs diagram, especially in splitting out data transformation etc from ETL. This is often missed but is a crucial foundational requirement.
Thanks Chris! I completely agree, I think people use ETL as a buzzword that has lost all meaning. ETL is a process/ approach, its not a technology. There is tech that facilitates it, but I find engineers dumb it down because they understand it (even if the rest of us don't). Approaching it from a hierarchy spells out what matters/ what doesn't and I hope I did a good job of that!
I just love this. Everybody continue publishing and speaking about data strategy, information architecture etc. We already got the technology and the people.
I love the hierarchy of needs diagram, especially in splitting out data transformation etc from ETL. This is often missed but is a crucial foundational requirement.
Thanks Chris! I completely agree, I think people use ETL as a buzzword that has lost all meaning. ETL is a process/ approach, its not a technology. There is tech that facilitates it, but I find engineers dumb it down because they understand it (even if the rest of us don't). Approaching it from a hierarchy spells out what matters/ what doesn't and I hope I did a good job of that!
Love the diagrams: you may like this one: https://www.junaideffendi.com/p/end-to-end-data-engineering?r=cqjft&utm_campaign=post&utm_medium=web
Love this one, definitely using it for my upcoming article on Data Engineering
I just love this. Everybody continue publishing and speaking about data strategy, information architecture etc. We already got the technology and the people.
Yup, the technology and the people needs to be underpinned by good thinking and approaches to these things!