Slow down to speed up: so much has changed in 6 months’ time

· Source: The Pragmatic Engineer · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering · Depth: Intermediate, medium

Summary

The software engineering landscape has undergone a rapid transformation in the last six months due to advanced AI agents like Opus 4.5 and GPT-5.4. This shift is exemplified by Meta's recent "most embarrassing outage," attributed to AI-generated, AI-reviewed code and significant cuts to security and quality teams. Data indicates teams using AI agents now ship 5x more pull requests than two years ago, and developers using AI harnesses produce 2.5x more code, increasing from 3,500 to 8,600 lines on average. Pull request sizes are also up 3x, with more AI changes accepted without human review. Major tech companies like Anthropic, OpenAI, Google, and Uber are deeply integrating AI into their workflows, with Anthropic reporting 70-90% of its code generated by Claude. Even traditional companies like Cisco and JP Morgan Chase are heavily investing in AI developer tools, indicating widespread adoption despite potential risks to software quality and reliability.

Key takeaway

For engineering leaders overseeing AI integration, you must balance rapid development with robust quality assurance. While AI agents significantly boost individual output, relying solely on AI-generated and AI-reviewed code risks critical system failures, as seen with Meta's outage. Prioritize investing in human-centric review processes and dedicated integrity teams, rather than solely reallocating resources to AI training, to prevent eroding core product stability and maintain long-term reliability.

Key insights

Rapid AI agent adoption boosts individual dev output but risks software quality and organizational integrity without human oversight.

Principles

Method

Companies integrate AI agents via internal tools, AI code review, and parallel agent execution, often replacing PRDs with prototypes and automating bug fixes.

In practice

Topics

Best for: CTO, VP of Engineering/Data, Executive, Software Engineer, AI Engineer, Director of AI/ML

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Pragmatic Engineer.