Tidewater blog https://saas.phoenixcodes.org/blog Notes on data freshness, lineage and alerting from the people who build Tidewater. en-us Wed, 14 Oct 2026 00:00:00 GMT Late but green, when every job succeeds and the data is still stale https://saas.phoenixcodes.org/blog/late-but-green https://saas.phoenixcodes.org/blog/late-but-green Wed, 14 Oct 2026 00:00:00 GMT Most data incidents reach a dashboard through jobs that report success. Here is how to measure freshness directly and set expectations a team will trust. Data quality freshness monitoring dashboards Most data incidents reach a dashboard through jobs that report success. Here is how to measure freshness directly and set expectations a team will trust.

By Ines Duarte. Read the full post.

]]> How we build column lineage from SQL without running your queries https://saas.phoenixcodes.org/blog/lineage-from-sql https://saas.phoenixcodes.org/blog/lineage-from-sql Wed, 30 Sep 2026 00:00:00 GMT We read the SQL your warehouse already ran, parse it, and resolve every column back to its source. This is how it works, where it fails and how we check it. Engineering lineage sql parsing We read the SQL your warehouse already ran, parse it, and resolve every column back to its source. This is how it works, where it fails and how we check it.

By Tomas Lindqvist. Read the full post.

]]> A runbook for the dashboard that is wrong at 6 a.m. https://saas.phoenixcodes.org/blog/runbook-wrong-dashboard https://saas.phoenixcodes.org/blog/runbook-wrong-dashboard Wed, 16 Sep 2026 00:00:00 GMT A step by step routine for the moment someone says a number looks wrong, with the queries and API calls we use to find the cause in under 15 minutes. Guides incident response runbook freshness A step by step routine for the moment someone says a number looks wrong, with the queries and API calls we use to find the cause in under 15 minutes.

By Amara Nwosu. Read the full post.

]]> Alert fatigue is a routing problem, not a volume problem https://saas.phoenixcodes.org/blog/alert-fatigue-routing https://saas.phoenixcodes.org/blog/alert-fatigue-routing Wed, 02 Sep 2026 00:00:00 GMT Teams mute noisy channels because nobody in them owns the alert. Route each alert to the owner, hold the rest for a digest and the volume stops mattering. Product alerts ownership on-call Teams mute noisy channels because nobody in them owns the alert. Route each alert to the owner, hold the rest for a digest and the volume stops mattering.

By Hannah Cho. Read the full post.

]]>