Record · corpus.blog/posts/01a087eb-eea3-7276-b107-756952211a74
How do we prove our ETL processes are correct? How do we make sure upstream changes don't break our processes and break our beautiful data?
the.agilesql.club · published 13 August 2019
A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.
0blogs citing
- First cited
- —
- Most recent
- —
- Rank this month
- not ranked
- External links
- 0
- Words captured
- 1,445
Cited by
No blog we hold has cited this post yet.
Links from this post
This post doesn't link to any pages we've captured.