Billionaire founder of Minecraft slams anyone advocating using AI to write code as ‘incompetent or evil’

Markus 'Notch' Persson, creator of Minecraft, publicly warned against relying on generative AI to write code, arguing it undermines core programming skills and autonomy; he urged developers to 'Learn. Your. Craft.' The debate is unfolding as major tech firms report sizable AI adoption for coding—Google says over 30% of its code is AI-generated, Microsoft cites 20–30%, and some AI startups claim near 100%—highlighting potential implications for engineering headcount, productivity and talent composition. Persson’s profile (Minecraft has sold 300M+ copies; acquired by Microsoft for $2.5B; Persson’s net worth ~ $1.5B) underscores the cultural resonance of the critique even as industry leaders advocate widespread AI integration.

Analysis

Market structure: AI-driven coding materially amplifies demand for AI compute (NVIDIA NVDA) and cloud AI platforms (MSFT, GOOGL) while compressing demand for labor-intensive outsourcing and junior developer services (near-term headcount reductions of 10-30% possible in affected vendors). Pricing power concentrates with GPU suppliers and hyperscalers who sell integrated AI stacks; expect gross-margin expansion of 100–300 bps over 12–24 months for cloud providers if adoption accelerates above 20–30% of code workloads.

Risk assessment: Tail risks include a regulatory clampdown on AI safety/data use within 6–18 months, major production failures (high-severity outages/hallucinations) that could trigger liability suits, and supply-chain shocks for GPUs (chip shortages raising NVDA ASPs >20%). Immediate (days) volatility will be earnings-driven; short-term (weeks–months) adoption signals matter; long-term (years) implications hinge on labor-market displacement and capex cycles for datacenters.

Trade implications: Favor concentrated exposure to NVDA and cloud names while hedging operational risks — NVDA captures structural GPU demand; MSFT/GOOGL capture software/service monetization and enterprise lock-in. Tactical option structures (bull-call spreads on NVDA around key earnings) reduce cost-of-entry; rotate out of legacy IT services/outsourcers (e.g., CTSH, INFY) where automation threatens revenue per head.

Contrarian angles: Consensus underestimates friction — quality, security, and regulatory costs will slow full replacement of hand-coding (a multi-year, not immediate, process), creating intermittent windows to short overbought hardware rallies. Historical parallels: ERP/cloud adoption helped hyperscalers but devastated mid-tier vendors over 3–5 years; expect similar multi-year bifurcation. Unintended consequence: rising demand for testing, observability, and AI-safety tooling — a secondary growth pocket to watch.

Key Decisions for Investors

• Establish a 2–3% portfolio long position in NVDA over the next 30 days: use 1% in equity and 1–2% via Jan 2027 LEAP calls (target delta ~0.5–0.65) to capture secular GPU demand; trim 50% on a 30% rally and re-evaluate if NVDA implied vol drops >15 vol points.
• Build 1.5–2% long exposure split equally between MSFT and GOOGL (0.75–1% each) to play cloud AI monetization; sell 1–2 month 10% OTM covered calls on 25% of these holdings to harvest elevated premium while maintaining core exposure.
• Initiate a relative-value pair: long NVDA (1.5% notional) / short CTSH (1.5% notional) as a 6–12 month trade; rationale — capture hardware/cloud upside vs. headcount-levered services downside if AI reduces billing rates by >10% within 12 months.
• Buy 3–6 month NVDA call spreads (25–40% OTM) ahead of next two earnings windows to play upside with defined risk; size at 0.5–1% portfolio notional and target >2x payoff if shares move >25% on positive adoption metrics.
• Allocate 0.5–1% to growth-in-education/AI-upskilling names (COUR) and 0.5–1% to data platforms (SNOW) on >10% pullbacks; add if company-reported AI adoption metrics (percent revenue from AI features) exceed 10% in next two quarters.