![rw-book-cover](https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F69a5e51b-896e-4f37-8653-25ff97265e6e_1090x1547.png) ## Metadata - Author: [[winnie|Winnie]] - Full Title:: Lessons From the Warehouse - Category:: #🗞️Articles - URL:: https://roundup.getdbt.com/p/lessons-from-the-warehouse - Finished date:: [[2023-09-19]] ## Highlights Regarding [[Process allergy|Process Allergy]]: "structure" is not "process". > Think about a dbt DAG, and for simplicity, let’s say we’re running [1 thread](https://docs.getdbt.com/docs/core/connection-profiles#understanding-threads). We’ve got two unrelated models called `customers` and and `events`. Now even though they could, in theory, run in parallel, practically they can’t; one will have to wait until the other is built and tested to start running, because we can only operate on one thread at a time. Our empowered decision makers are like our threads when we create process. > Now imagine we throw the thread count wide open to 128 threads, but we implement a set of automated tests, pre-commit hooks, linters, CI/CD, and a formatting tool that enforces our style guide. Now we’ve created more *structure*, but minimized process. > Structure, the actions and elements of a single layer of process, sans the control mechanisms and hierarchy, is a *positive force.* ([View Highlight](https://read.readwise.io/read/01hanr73qv2whbb7nd7jgk185r)) > *structure is not process,* and structure helps **more people** **go faster** ([View Highlight](https://read.readwise.io/read/01hanr82det552mz8z61yjcjez))