Subtitle: An iOS performance investigation I actually did, end-to-end through Claude Code, with MCP-driven simulator control, xctrace Time Profiler, and the Memory Graph CLI. What the AI handled, what it didn't, and how my workflow changed. Hey folks, let me walk you through an afternoon I had debugging an iOS perf ticket I'd been postponing for three weeks. Motivations, obstacles, dead ends, and wins included. Quick setup. Working on an app that uses SwiftUI quite a bit. The SavedItems tab was getting slow after about 15 location detail screens. Probably a memory leak. Probably something related to SwiftUI navigation. Probably "easy" after I stopped to analyze it. Spoiler: None of those hypotheses were correct. The investigation took an entire afternoon and resulted in three independent corrections and three pull requests. And most of my time at the keyboard was spent reviewing what Claude had just done, not typing. This text is not an account of how AI changed someone's life (please don't).…