AI is turning developers into pull-request machines, the numbers are real, the stories are everywhere. But shipping code and building software aren’t quite the same thing. Something in the math doesn’t add up.
Shipping fast, breaking slowly


AI is turning developers into pull-request machines, the numbers are real, the stories are everywhere. But shipping code and building software aren’t quite the same thing. Something in the math doesn’t add up.

AI is making developers faster, the dashboards say so, the line counts confirm it. But writing code was never where the time actually went. Somewhere in that speed, something got lost. Nobody put it on the dashboard.

After a year of professional Rust, one pattern stands out in how the community talks about the language: the comparisons always win, but only because they pick the wrong opponent. Go, the one language that belongs in the same conversation, is conspicuously absent.

The demo was impressive. The slides were polished, the use cases relevant. But the moment questions started, there was nothing behind it. Producing content and having knowledge are not the same thing, and the gap between them may be wider than we think.

Doing the right thing is hard and demands courage. Doing the politically right thing is so much easier, and that’s the problem.