The article discusses how database deadlocks can cause application downtime, explaining the mechanics of deadlocks in MySQL and PlanetScale's approach to handling them. It covers common causes, detection strategies, and best practices for minimizing their impact on production systems.
Background
- **PlanetScale** is a serverless MySQL database platform built on top of **Vitess** (the same horizontal-scaling system used by YouTube). It lets developers treat MySQL like a cloud-native service.
- A **deadlock** in a database happens when two or more transactions each hold locks the other needs, so none can finish. MySQL resolves deadlocks by killing one transaction (the "victim"), which can break the app that issued it.
- The article walks through a real outage where an application change (adding a new index) and MySQL’s internal lock-ordering caused frequent deadlocks under load. The author explains why the deadlock happened, how to reproduce it, and what strategies (e.g., explicit lock ordering, reducing transaction scope) prevent it.
- For readers following backend/infra discourse: this is a classic "innocent config change + subtle DB behavior → production crash" story, and the post serves as a case study in debugging MySQL deadlocks in a Vitess/PlanetScale environment.
Max Weinbach says he had early access to OpenAI's new model GPT-5.6 Sol, calling it his favorite model by far. He highlights that it never gives up and will keep reasoning until it's done. OpenAI announced that GPT-5.6 Sol, along with Terra and Luna, will launch publicly on Thursday, with preview access expanding globally now.
The US government ordered Anthropic to suspend access to its Fable 5 and Mythos 5 models for all customers, citing a potential jailbreak technique that involved asking the model to review a codebase for vulnerabilities—a capability Anthropic says is available in other public models. Access was abruptly cut off on June 12.
Andrej Karpathy announces the release of Claude Fable 5, the same underlying model as Mythos but with added safeguards. He calls it a major step forward, particularly for long problem-solving sessions on difficult tasks, and describes it as state-of-the-art on nearly all benchmarks with exceptional performance in software engineering, research, and vision.
Roman Storm warns that the legal theory in his case could set a precedent making open-source developers liable for how others use their code, potentially criminalizing the mere publication of privacy, messaging, or crypto tools. He notes that developer Michael Lewellen cannot publish lawful code due to prosecution fears, and argues this chilling effect extends beyond any single case.
Meta's engineering culture is deteriorating under Mark Zuckerberg and Scale AI CEO Alexandr Wang, who have introduced keyboard tracking, reassignments to data labeling, and AI-centric performance metrics. Critics argue this incentivizes performative AI use, drives away experienced engineers, and contributed to a major Instagram hijacking incident caused by AI-written and AI-reviewed code.