
Shipping Code You Never Read

Stop being skeptical about AI for development with Charity Majors
Topic 4 of 17
Published Aug 12, 2026 · Clip 12:24–19:22 (6:58)
Charity and the host explore what would make shipping unread AI code acceptable: provenance, harness testing, and tandem human/AI comparison to build trust over time. They discuss Chad Fowler's Phoenix architecture ideas that when rewriting is cheap, editing in place becomes risky, so code should be replaced like immutable infrastructure (code is cash, pets vs. cattle). Charity stresses the economics—generating 10,000 variants is cheaper than writing once—and shares the painful two-year Parse rewrite from Rails to Go as a lesson about lost contracts. They close with the sysadmin analogy: the role disappeared but sysadmins adapted and became engineers, PMs, and salespeople.