Databricks Blog

3 stories

Databricks Blog

Databricks BlogToolsThe Enterprise Case for Open-Weight Models on Databricks As field engineers at Databricks, we spend our days inside enterprise AI deployments,...

11.04

Databricks Blog

Databricks BlogToolsClaude Platform now supports native OpenTelemetry observability in Databricks MLflow An agent can return a plausible answer while missing an important finding or reading the same source repeatedly...

11.03

Databricks Blog

Databricks BlogToolsLakebase Postgres is now generally available on Google Cloud We're excited to announce that Lakebase Postgres is generally available on Google Cloud...

11.02

The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around two hundred sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo