Ai

224 posts filed under Ai.

Postgres handled it fine. Until the agent started issuing thousands of embedding lookups a second.

We changed the questions in the postmortem, and the recurring outage stopped recurring.

Data platform changes have a good window and a bad one. Funding milestones tell you which is which.

We scored a client's pipelines on cost against consumption. About 1 in 5 had a monthly bill and zero consumers.

Duplicate invoices came from the recovery, not the outage. The retry replayed 40 minutes into a double-counting sink.

A company at 40 people needs senior data judgment about 2 days a week. Full-time is the wrong container.

Nobody owned the orders table. Everyone had opinions about it in the incident channel.

Your engineers are already learning AI at work. The only question is whether it's sanctioned.

A failure that cost one dashboard last year now takes out 40 downstream jobs. The platform grew. The alerts didn't.

Half the "Head of Data" searches I see are two different jobs wearing one title.

Want expert eyes on your data architecture?