Delivering Care through Data with Trust, Understanding
summary
Clear, practical examples of what works: using PowerShell and DevOps pipelines to enforce data lineage, versioning and alerting; scripts that replace fragile Excel workflows and stop recurring errors; automated documentation that actually updates; privacy checks and simple audit hooks for compliance. Concrete surprises include a miscomputed median that falls from 90 to 7 once fixed, a dataset showing −178 hospital nights, and a bogus “two million cars” sales claim. Focus is on tools, failures found, and pipelines that succeed.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:14Excel hell impact
- 5:08Introversion in IT
- 9:23Data misconceptions
- 13:16Old software attitudes
- 16:05From info to knowledge workers
- 18:34Data insights driving change
- 22:03Data lakes vs Excel puddles
- 26:18Excel chaos
- 29:06Fear of missing out and PowerShell benefits
- 31:56Trust in data delivery
- 35:26Visualizations flexibility
- 37:12Choosing battles
- 40:04Automating tasks
- 41:50Data confidence survival
related talks
34m#DataDrivenDevOps
42mData-Driven DevOps
42mBringing Software Engineering Rigour to Data, DataEngBytes 2022
30mDevOps For Data Teams
23mBridging the DevOps Gap in Modern Data Teams
30mDataOps: Much More Than DevOps for Data
16mTransforming Public Sector Observability
30mA Devops Approach to Data: A Tale Through the Trenches in Search of a Cloud Data Revolution