dbt snapshots are useful when you genuinely need point-in-time history, but they introduce complexity, brittleness, and a heavy maintenance and backup tax. this post is a reminder that less is more, simple is better, and you should never build a snapshot on top of another snapshot.
a guide on using dbt snapshots to track slowly changing dimensions, including lessons learned from migrating away from custom merge strategies.
how i use dbt tests, including not_null, unique, relationships, accepted_values, and singular tests, with examples you can copy to catch data issues early
i walk through how dbt docs work, including what they generate, writing descriptions and doc blocks, persist_docs, and hosting them free on github pages