Chad Sanderson
where else to find them
what they talk about
where they keep going back
no series more than once — all 4 in the filters
on a stage with
all 5 in the filters
who talks about the same things
- Mikiko Bazeley6 talks
- Jean-Georges Perrin8 talks
- Jochen Christ4 talks
- Joe Reis16 talks
- Michael Nygard11 talks
- Ryan Boyd11 talks
| title | conference | date |
|---|---|---|
| Panel Discussion | DataEngBytes Melbourne 2023 | 2023-08-31 |
Debate over when to add guardrails gives concrete rules: treat data contracts as codified APIs (schema, SLAs, ownership) when data is a product; delay heavy… | ||
| DataEngBytes 2023 - BRI-T1-01 - Chad Sanderson | DataEngBytes Brisbane 2023 | 2023-08-29 |
Argues that API-style data contracts — a YAML contract spec plus CI/CD PR checks tied to schema, semantics and SLAs — prevent churn and costly outages at… | ||
| Panel Discussion | DataEngBytes Brisbane 2023 | 2023-08-29 |
Argues data engineering expands beyond pipelines into data modeling and ongoing quality work, with concrete ML pitfalls like target leakage and distribution… | ||
| Panel Discussion | DataEngBytes Sydney 2023 | 2023-08-25 |
Panelists argue MLOps differs from DevOps because models are probabilistic, tightly coupled to data quality and versioning, and can produce different outputs… | ||
| DataEngBytes 2023 - SYD-T1-03 - Chad Sanderson | DataEngBytes Sydney 2023 | 2023-08-25 |
Defines data contracts as API-like agreements that declare schema semantics and SLAs and enforces them programmatically via YAML contract per resource with a… | ||
| DataEngBytes 2023 - PER-T1-01 - Chad Sanderson | DataEngBytes Perth 2023 | 2023-08-22 |
Claims that YAML contracts in Git plus CI/CD GitHub Actions enforcing tiers turn data quality from reactive toil into preventative control by validating… | ||
| nothing matches | ||