Treat Backfills as Production Code to Avoid Fragile One‑offs
Backfilling isn’t a post‑mortem script, it should run through the same extract‑raw‑transform pipeline as daily loads, toggled by config flags. By treating migration and historical ingestion as production jobs (Opto uses Dagster), teams eliminate brittle one‑offs, improve correctness, and cut the endless firefighting that follows ad‑hoc backfills.