Testing Claude Code's Opus 4.5 left me stunned by how quickly it generated functional software. The tool’s speed sparked a debate that Marc Andreessen likens to a “Mexican standoff”: engineers feel they can design, product managers think they can code, and designers assume they can own architecture. That convergence threatens traditional role boundaries and could upend team culture across the organization.

Kent Beck warned on X that “90 % of my skills just dropped to $0,” while the remaining 10 % skyrocketed in leverage. Ben Werdmuller echoes this, saying AI moves the focus from rote implementation to judgment. He urges engineers to master goal‑setting, user insight, experience clarity, and robust architecture—areas traditionally claimed by PMs, designers, and leadership alike for modern teams.

Founders I spoke with confirm the shift: a head of product now ships dozens of PRs himself, and hiring pipelines favor generalists over specialists. Ghost founder John O'Nolan remains optimistic, expecting new roles to emerge as old ones compress. In practice, teams like Tighten’s are already pairing PMs with engineers in live LLM sessions, co‑owning pull requests and accelerating delivery for the whole product lifecycle.