Database Schema Drift Starts With One Manual ALTER

Sat, 17 Oct 2026 00:00:00 +0000

It’s 2 a.m. and checkout is timing out. Someone finds the slow query, adds an index on production by hand, and the graphs go green. Nobody writes a migration for it. Three weeks later a deploy runs a migration that drops and rebuilds that table, the index is gone, and checkout times out again. Or the other way round: a hotfix makes a column NOT NULL on production only, and the next release, which was tested against staging, fails every insert that leaves it empty.

AI Models Drift Under Your App and Nobody Tells You

Sat, 17 Oct 2026 00:00:00 +0000

Your app calls an AI model by name. It’s a string in a config file, gpt-4o or claude-sonnet-4-5, and it was right the day someone typed it. The model behind that string lives on somebody else’s servers, on somebody else’s schedule.

Providers retire models. They rename them, or point an alias at a newer one. They cut a context window, add a retirement date, move a model from active to deprecated, raise the price per token. None of that is a secret. It goes into a changelog, a deprecations page, maybe an email to whoever signed up for the account three years ago. And the team that owns the app finds out from a stack trace.

Explainer on RadarModel.com

Database Schema Drift Starts With One Manual ALTER

AI Models Drift Under Your App and Nobody Tells You