PinnedInData Engineer ThingsbyCG·Oct 17, 2025Why Data Product Management Is Nothing Like Software Product ManagementAnd the five competencies you need to succeedA response icon7A response icon7
PinnedInData Engineer ThingsbyCG·Oct 9, 2025You’re Not Building Data Products. You’re Building Infrastructure (And Why That’s a Problem)Why most data teams confuse infrastructure with impact — and how to fix itA response icon10A response icon10
InPragmatic Data EngineeringbyCG·Oct 14The 5 Data Engineering Skills That Will Matter Most in 2028The tools will change. The judgment you build now is what compounds.
InPragmatic Data EngineeringbyCG·Oct 10How to Become an AI-Native Data EngineerAI-Assisted Is Not AI-Native
CG·Sep 11Data Contracts in Practice: What Actually Happens Between "We Wrote a Schema" and "Nothing Broke"A working example of a contract, and the CI/CD pipeline that enforces it
InPragmatic Data EngineeringbyCG·Sep 8Data Product Strategy: Why You Need One (And How to Build It)How I learned to stop reacting to whoever yelled loudest
InPragmatic Data EngineeringbyCG·Sep 5Why Data Product Management Is Nothing Like Software Product ManagementAnd the five competencies you need to succeedA response icon2A response icon2
CG·Sep 1Schema Strategies: The Data Engineering Decision Most Teams Never Make ExplicitlyDynamic, inferred, typed, contract-driven, and everything in between
InData Science CollectivebyCG·Aug 24The Pragmatic Programmer Is More Relevant Than Ever in the Age of AIWhy clean repositories, DRY code, and software craftsmanship have become competitive advantages for AI-assisted development.A response icon1A response icon1
InData Engineer ThingsbyCG·Aug 17The Open Data Contract Standard: Is This the Missing Interface for Data Engineering?Why ODCS could give data engineers a common language for schemas, quality, SLAs, and ownership — and where it still falls shortA response icon1A response icon1
