DuckDB changed what counts as a "simple query". Not long ago, joining data from different places usually meant building some awkward temporary workflow first. Postgres table here. Parquet files there. Some files in S3. Then came the usual mess: exports, staging tables, notebooks, temporary scripts, local folders with names like final_final_2 , and a small amount of shame. DuckDB made a lot of that feel unnecessary. It can read Parquet directly, work with object storage through httpfs , and connect to PostgreSQL through the PostgreSQL extension. A lot of work that used to require exports or a small ETL job can now start as plain SQL. That is the good part. The annoying part starts after the query works. The question is no longer only: Can this engine query the data? Often the harder question is: Can this workflow be trusted again next week without rebuilding everything around it? DuckDB solved a large part of the query engine problem. The workflow around it is still scattered.…