Two movements meet: AI is getting production responsibilities, and production data is flowing through AI. Anthropic’s September report, malicious routers, training data provenance and model drift show what to verify before an AI reaches production.
A preregistered ETH Zurich study found that computer science knowledge, not writing skill, is the strongest predictor of vibe coding success. Here is what that does and does not say about DHH’s claim that programmers can be worse at AI coding than people who cannot code.
GPT-6-Astra XHIGH sits alone on the DeepSWE cost-performance frontier, and an older model beats a flagship tier. Follow-up: DeepSeek V4.1 Flash hits 98% of Astra’s score at 1.4% of the cost.
AI products moved from the answer arrives to the answer flows. What streaming inference changes in capacity planning: TTFT, token throughput, concurrent streams.
DHH told Lex Fridman that for some problems, programmers do worse with AI coding tools than people who cannot code. What the claim actually covers, and what it means for teams adopting AI agents.
Ox Alpha is a free anonymous-provider preview on OpenRouter. I explain how I would test task quality, agent reliability, cost, privacy, and fallback readiness before production use.
A volunteer red team filed 4,962 AI findings across 390 repositories in 27.5 hours, and not one came from a public US frontier model. Not a capability gap: the capable versions sit behind identity gates. Refusal policy is now where the labs differentiate, and it belongs on your dependency list.
Knowledge distillation is a large model teaching a small one, and it works almost exactly like school: soft labels instead of a bare answer key, pairing weeks instead of reports, and a tutor who marks your own attempt rather than a textbook of last year’s solutions. The limits map too, and the last one costs money when you size the hardware.
A frontier lab optimizes an absolute target and has to explore. A challenger optimizes a distance to the leader and can exploit. That is the whole cost asymmetry, and it shows up in GPU hours and in a bike race.
I used whisper.cpp on an RTX 5070 to transcribe about 100 hours of podcasts in roughly three hours, then turned the Markdown output into a searchable prompt knowledge base.