How Do We Handle AI Opponents?
summary
Argument: resistance comes from fear, not failure; examples: an AI-generated portrait with six fingers from shutt, buggy code and two new errors from chat GPT, and QA veterans claiming AI creates unacceptable edge cases. Proposed tactic is pragmatic change management: focus on early adopters, drive adoption until get >50% adoption in a team so holdouts lose informal power, then offer a face‑saving reintegration path for resisters rather than exhausting effort to convince them up front.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:48Skepticism toward AI
- 3:58Change management for AI resistance
- 6:31Focusing on supporters
- 8:18Reintegrating opponents
- 10:27Adapting to AI as industry
related talks
20mHuman above AI
28mBuilding an AI-Ready Workforce
41mSurviving and Thriving with AI in QA
15mManaging Your AI-Driven Manager
27mEngineering in the Age of AI: Making AI Work for Us, Not Replace Us
39mAI is Coming, What Now?
40mThe Developer RenAIssance: The Humans Powering the Age of AI
55mPanel Discussion: Will AI Kill Programming?