> Two dbt repositories. One handles data engineering transformations. The other handles business-level transformations.
This deserves its own article on the importance of two transformation repos. The separation of concerns keeps the two adaptable to changes without being entangled. I'm currently building a greenfield lakehouse with this pattern.
Building stakeholder trust through the status page is the leverage here and that will continue to compound. Also, scoping the page to the parts the stakeholders are interested in is so important. It wouldn't get looked at otherwise or you'd end up with the same amount of questions/messages.
Question though: how do you handle the triage call? Whether to "fix it quietly" or "declare it publicly." Who owns that?
Great question, Alex. We have a set of business critical reports (about 3 of them). So, if one of these reports gets impacted, and we declare an incident. Most other things are not used that much anyway. We still post a message, but don't call it an incident.
> Two dbt repositories. One handles data engineering transformations. The other handles business-level transformations.
This deserves its own article on the importance of two transformation repos. The separation of concerns keeps the two adaptable to changes without being entangled. I'm currently building a greenfield lakehouse with this pattern.
This is a great idea for an article. And, I’d absolutely love to share notes some day.
Building stakeholder trust through the status page is the leverage here and that will continue to compound. Also, scoping the page to the parts the stakeholders are interested in is so important. It wouldn't get looked at otherwise or you'd end up with the same amount of questions/messages.
Question though: how do you handle the triage call? Whether to "fix it quietly" or "declare it publicly." Who owns that?
Great question, Alex. We have a set of business critical reports (about 3 of them). So, if one of these reports gets impacted, and we declare an incident. Most other things are not used that much anyway. We still post a message, but don't call it an incident.
Thanks for the clarification, Yordan.
Of course, I hope that really helps