He was coding at 12 and became one of Google’s youngest ever CMOs—but now says Gen Z are better off ice skating than learning to code

The article argues that AI is making coding less important as a career entry point, with former Google CMO Alon Chen saying creativity, resourcefulness, and execution matter more than technical coding skills. It cites examples such as Microsoft already generating 30% of code with AI and forecasts from industry leaders that AI will continue commoditizing execution. The piece is more a cultural and workforce-skills commentary than a market-moving event, with limited direct financial impact.

Analysis

The market implication is less “coding is dead” than “software labor is being repriced from scarce craft to abundant utility.” That compresses the wage premium for junior engineering talent first, then pushes differentiation up the stack into product sense, distribution, and domain expertise. The second-order winner is any platform that turns non-technical operators into builders; the loser is the long tail of outsourced dev shops and credential-heavy entry-level hiring models that relied on labor arbitrage.

For listed names, this is mildly constructive for MSFT, SNOW, and IBM because each can monetize the shift from code production to workflow orchestration and decision support. The bigger issue is not demand destruction but mix shift: AI-assisted development may expand total software creation while reducing seat counts for low-value engineering roles, which supports cloud consumption but could pressure services margins and near-term hiring intensity. PEP and NFLX appear only tangentially exposed through more productive marketing/content workflows, so any earnings impact is slower and harder to underwrite.

The contrarian angle is that the “creativity premium” narrative may be overstated in the short run. Most enterprises still bottleneck on security, data quality, compliance, and integration, so AI won’t eliminate technical labor so much as change where it sits in the stack over the next 12-24 months. If anything, the first-order trade is not to short programmers broadly, but to own the tools that reduce the cost of building while selling the governance layer that prevents AI-generated mistakes from scaling.

Catalyst-wise, watch for guidance changes from software vendors tied to developer productivity metrics, and for a pickup in enterprise AI copilots that prove ROI in 2-3 quarters rather than years. If those deployments keep showing faster cycle times without major defect spikes, the market will increasingly re-rate platform and infrastructure names over labor-heavy IT services.

Key Decisions for Investors

• Long MSFT vs. short a basket of legacy IT services over 3-6 months; thesis is that AI-assisted workflows accrue to platform vendors while labor-arbitrage models face margin compression.
• Add to SNOW on 1-2 quarter pullbacks; if AI-driven analytics and governance adoption lifts enterprise workloads, upside can surprise on consumption growth while downside is limited by current strategic positioning.
• Buy a small IBM call spread 6-12 months out; the market is underpricing the optionality from AI governance and enterprise transformation spend, with asymmetric upside if clients pay for compliance-heavy deployment.
• Avoid shorting software broadly; instead, if you want expression on the labor displacement theme, use a basket short on lower-end dev/IT services names rather than GOOGL/MSFT, where AI leverage is more likely positive than negative.
• For PEP and NFLX, treat this as a neutral operational efficiency story rather than a fundamental catalyst; any position should be catalyst-driven only if management signals material AI-enabled SG&A leverage in coming quarters.