The leader track π€ Β· for C-level, managers & curious minds Β· 6 x 45 min Β· no code to write
Thinking mode: why a warehouse is a copy on purpose, what "one truth" really costs, how to read the vendor landscape, why bills explode, and what the AI era changes - each session ends with questions to ask your data team.
Why a warehouse
OLTP vs OLAP in plain business terms, and the copy idea: a warehouse is your data duplicated on purpose, restructured for big questions.
β Leader 2 Β· easyThe shape of a warehouse
The three layers every warehouse has, and the star schema - why facts and dimensions are the floor plan behind every dashboard.
βοΈ Leader 3 Β· mediumThe one-truth problem
Why two honest teams report two different revenues: metric drift, conformed dimensions, and what "single source of truth" actually takes.
π Leader 4 Β· mediumThe buy landscape
Warehouse vs lake vs lakehouse, and the engine landscape - Snowflake, BigQuery, Redshift, Databricks - as decisions, not logos.
πΈ Leader 5 Β· mediumCost and performance
Why warehouse bills explode, the four levers that control them, and the questions that keep your team honest about spend.
π€ Leader 6 Β· mediumThe warehouse in the AI era
Serving ML and AI from the warehouse, why governed data is the AI moat, and a crawl-walk-run plan you can actually fund.
The builder track π οΈ Β· for practitioners Β· 10 sessions x 45 min (b10: 60) Β· live DuckDB in your browser
One running project: Daybreak - the coffee-subscription brand from learn-sql-with-phoebe, grown up. Its OLTP database plays the source system, and session by session you build its first warehouse: staging, star schema, SCD merges, loading patterns, marts, Parquet round trips. Every page runs real DuckDB via WebAssembly - editable SQL over 300,000 rows. The engine loads once from a CDN (about 8 MB, the one network dependency); everything after that is offline.
Row store meets column store
Feel the difference, not read about it: columnar storage vs the row-by-row app database, with DuckDB live on 300k rows.
ποΈ Builder 2 Β· mediumArchitecture and the staging layer
The layered warehouse, and staging as the airlock: land Daybreak's raw tables, type the text dates, and add quality gates.
π Builder 3 Β· mediumFacts and dimensions
Declare the grain, split measures from context, and sketch Daybreak's star schema - the modeling move everything else hangs on.
π Builder 4 Β· mediumBuilding dimensions
Surrogate keys, a generated dim_date, and clean conformed dimensions - built and queried live against the staged tables.
π°οΈ Builder 5 Β· hands-onSlowly changing dimensions
SCD Type 2 for real: customers move city, plans change price - track history and answer point-in-time questions correctly.
π Builder 6 Β· hands-onLoading patterns
ELT, full vs incremental loads, and the idempotent MERGE - run the same load twice and prove nothing breaks.
πͺ Builder 7 Β· hands-onMarts and serving
Ship the warehouse to the business: department marts, views and rollups, and the finance-vs-marketing revenue question settled.
β‘ Builder 8 Β· hands-onPerformance and cost
Partition pruning, sort orders, and the cost levers - measure real scan savings live, then map them to cloud pricing.
π§ Builder 9 Β· hardestLakehouse and the modern stack
Parquet round trips live in the browser, table formats, One Big Table vs vault vs star - where the field is heading and why.
π Builder 10 Β· hardest Β· 60 minCapstone: the whole warehouse
Assemble the full pipeline end to end - raw to staging to star to marts - and close with a board pack built on your own warehouse.
Best after learn-sql-with-phoebe - the Daybreak database comes from there. For schema-design depth see learn-data-modeling; for pipelines see learn-data-engineering.
Built from IBM Data Warehouse Fundamentals, DeepLearning.AI Data Engineering (Joe Reis), 365 Data Science Intro to Data Warehousing, and vendor deep dives - certificates stay official.
The knowledge map π§
Both tracks at a glance - hover a session to spotlight its concepts, click any node to jump in.