Will Claude Code ruin our team? Short answer: it will scramble roles quickly, then force better discipline. Read Justin Jackson’s piece: https://justinjackson.ca/claude-code-ruin
Short-term: chaos. Agents will open PRs with plausible but brittle code, duplicate features, and surface security issues. Expect noisy CI, flaky merges, and PMs debugging imports. Friction, not apocalypse.
Long-term: role shifts, not replacements. PMs become spec+acceptance authors. Designers own visual tests. Engineers own architecture, tests, infra, and guardrails. The teams that win treat AI as a junior dev, not a replacement.
Practical checklist for teams: 1) ticket-first (spec + tests) 2) mandatory human review on every AI PR 3) pre-merge CI + SAST 4) audit keys (BYOK) & logs 5) keep tickets small so agents stay in scope. Start with these.
Top comments (0)