Gergely Orosz · 9 min read · AI & Product
Stop being skeptical about AI for development with Charity Majors
Read the original on newsletter.pragmaticengineer.com →
In this episode, Charity Majors discusses how AI has evolved from skepticism to a foundational tool in software engineering, reshaping code generation, reliability, and the need for stronger verification and observability. The conversation highlights turning points like Claude Code, the cloud-era analogy for AI's impact, and the reality that engineers may soon ship code they haven't read, placing engineering discipline at the center of confidence.
Key Takeaways
- Skeptics should still learn to use AI (vibe coding) to critique it effectively rather than dismiss it outright.
- The turning point came with Claude Code and Opus 4.5, turning AI harnesses into serious infrastructure rather than mere automation.
- AI's impact on software in 2025 is akin to the cloud's impact in 2010—mainstream and transformative for the infra layer.
- Past hype (COBOL, neural nets, no-code/low-code) explains why early skepticism was warranted, highlighting the risk of over-promising.
- Engineering will increasingly ship code they haven't read; verification, observability, and disciplined practices become essential to ship with confidence.
Excerpt
Stream the latest episode Listen and watch now on YouTube , Apple , and Spotify . See the episode transcript at the top of this page, and timestamps for the episode at the bottom. Brought to You by • Antithesis – turbocharge testing of your systems by running your whole system under aggressive fault injection. There’s good reason teams like Jane Street, Fly.io, and the etcd community rely on Antithesis. Learn more. • Buildkite – the CI platform trusted by OpenAI, Anthropic, Cursor, Meta, Uber, NVIDIA , Airbnb and many more. When CI volume becomes an architecture problem, you deserve…