posts · 2026-06-11

The reason to click: rsync maintainer Andrew Tridgell's response is honest. He's getting older, AI-discovered vulnerabilities are piling up, and he can't patch them all manually. So he flipped the model: Claude writes the code, he writes the tests. The community fears AI-introduced bugs, but Tridgell's logic is that future attacks will be AI-driven too—manual defense is less realistic, and stricter testing makes the new approach safer. I'd discount this a bit because the post doesn't specify how much of the codebase Claude generated—the whole release or just some modules? No test coverage numbers either. But this points to a real trend: unpaid open-source projects facing a flood of AI-discovered vulnerabilities will eventually land on 'AI patches, human tests.' rsync is just the first to say it out loud.

The reason to click: the price-cut motive is concrete. Anthropic's Claude Code is getting woven into enterprise dev workflows and burning through tokens, directly pulling paying users away from OpenAI. OpenAI has the bigger consumer brand, but enterprise pays the bills, so this move targets developers. I'd discount this a bit for now. The WSJ piece doesn't give actual numbers or a timeline — just that cuts are being considered. If the drop is steep, it's a real win for API-heavy teams. If it's a modest tweak, it reads more like pre-IPO positioning. There's a second thread here: the biggest ChatGPT overhaul yet, aiming to turn it into a super-app spanning coding, AI agents, image generation, and business software, rolling out in the coming weeks. At the same time, the Codex team is pushing toward what their engineering lead calls a 'personal agent.' Taken together, OpenAI is trying to shift from single-model subscriptions to a platform that locks in enterprise workflows. Whether it works depends on actual integration details, and right now we only have the direction, not the product.

The useful bit here is the distribution play: Anthropic isn't just selling API access—it's routing Claude through DXC, one of the world's largest IT services firms that already runs the transaction and claims systems for major banks, airlines, and government agencies. DXC tested Claude internally first across 115,000 employees, using it to write over 95% of the code for OASIS, a new managed-services platform now serving 50+ customers. They claim a 10x speedup in development. I'd discount those numbers a bit—they come from Anthropic's own announcement with no independent verification, and the post doesn't specify what OASIS does or how much code we're talking about. But the direction makes sense: embedding Claude into existing IT service contracts is far more practical than asking regulated enterprises to build AI teams from scratch. For Anthropic, this opens a deep industry channel beyond the usual Microsoft and AWS partnerships. The rollout starts in insurance, code modernization, cybersecurity, and application services, with DXC training tens of thousands of Claude-certified engineers to work inside customer environments.

The 26.1k stars tell you the appetite for a fully open reproduction of DeepSeek-R1's reasoning is real. But the body only captured GitHub's navigation and metadata—no implementation plan, training data, progress, or scores. I'd treat this as a public collaboration scaffold and placeholder for now. The one concrete thing: Hugging Face is leading it, and the community is paying attention. Wait for a technical report or actual training scripts before judging fidelity.

This is worth a click because it challenges Git's core assumption. DeltaDB records every edit as an addressable delta and keeps the conversation that produced it side by side. You can jump from any line of code to the chat that created it, and agents can pull context from prior discussions. Multiple people and agents can edit the same worktree concurrently without committing first. I'd discount this a bit for now: we only have the blog post, the beta is weeks away, and there are no details on latency, conflict resolution, or storage overhead. But the direction is right. When more code is generated through conversation, version control should treat that conversation as a first-class artifact, not something you staple back on with PR comments. The Zed team already avoids PRs internally, so this solves their own workflow first. If the beta's real-time collaboration feels smooth, the context supply for agent workflows will be a clear step up from Git.

The numbers are what make this worth a click: $12B raised at a $41B valuation for a 7-month-old company with zero product. Prometheus wants to build an 'artificial general engineer' that compresses design-to-manufacturing cycles by 10x. Since you can't scrape factory floors like the web, the plan is to spend $100B buying traditional manufacturers to generate proprietary training data. The post doesn't say who led the round or how the money is split. I'd discount this heavily — a valuation leap from $6.2B to $41B with nothing shipped looks more like a capital narrative than an engineering milestone.

The reason to click: the structure changed. Lionsgate isn't just licensing Runway's tools anymore — it bought equity and is co-developing IP. First project is a short episodic series blending Lionsgate's existing IP with Runway's generative models. Lionsgate also becomes a presenting partner at Runway's AI Film Festival. Runway's CEO framed it bluntly: studios serious about AI treat it as a creative resource, not a cost-cutting tool. Lionsgate has been first-mover on this since September 2024 — first studio to partner with an applied AI research company, first to hire a Chief AI Officer, first to build internal AI infrastructure. I'd discount this a bit: the post doesn't give budget, episode length, distribution, or the equity stake size. It reads more like a statement of intent. But a studio taking equity in an AI video company is a stronger signal than a procurement deal.

The headline numbers are what make this worth a click: $150M initial commitment, 1,000 fellows, $85K salary plus benefits, placed full-time at 400+ nonprofits for a year. CodePath handles employment and training, Social Finance does evaluation—this isn't a loose experiment. What's missing: selection criteria and application timelines. The post names nine host orgs spanning food banks, veteran wellness, and marine conservation, so the range is real, but you can't act on this yet. I'd read this as the hands-on companion to Anthropic's AI-and-work policy framework, which they released the same day. It's less pure philanthropy and more a pilot for "how do you actually help people transition during AI-driven economic change." If they can show results here, that's more interesting than another API credit program.

This post lands because it strips the paint off a claim you've heard everywhere: Google, Anthropic, and OpenAI all say AI writes 75-80% of their code. David Curlewis points out the obvious—this is the same lines-of-code metric we spent two decades mocking, just with a better publicist. His contrast is sharp: a few years ago GitHub claimed Copilot made tasks 55% faster, a falsifiable outcome claim. Today's percentage numbers can't fail; they rise regardless of whether anything actually improved, because adoption is the one thing everyone agrees is real. The research conflicts he walks through are the useful bit. METR first found experienced devs 19% slower with AI in their own codebases, then walked it back in February 2026—developers now refuse to work without AI, so clean measurement is impossible. An NBER survey of ~6,000 execs found roughly 90% reporting no measurable productivity impact. Anthropic simultaneously claims engineers ship '8x more code' while their own RCT showed 17% lower comprehension and no significant productivity gain. I'd discount this a bit: it's a personal blog, not a systematic review, and the studies span different methods and populations. But it nails why 'percent AI-written code' is a vanity metric—and Block cut 40% of staff, Atlassian cut 10%, both explicitly citing AI, with numbers like these as the rationale.