AI Dev 26 x SF | Paul Everitt: The Shift to Agentic Engineering
Summary
Paul Everitt of JetBrains presented on "The Shift to Agentic Engineering," addressing critical challenges in current AI adoption within software development. He highlighted issues such as limited organizational value from AI, with productivity gains around 10% rather than 10x, and significant quality concerns including a 50% defect rate. Everitt also noted rising AI token costs, low developer trust (only 3% confidence in AI accuracy), negative impacts on engineer mental health, and governance complexities, particularly in Europe where 84% express sovereignty concerns. He argued that the industry's response, often involving layoffs and "AI washing," misses the opportunity to innovate. The proposed solution, Agentic Engineering, emphasizes building systems that build other systems, augmenting human capabilities, and returning to core engineering principles like robust systems design. This approach involves practical elements such as spec-driven development, rigorous evaluations, harness engineering, specialized tooling, and red-green testing.
Key takeaway
For Directors of AI/ML and engineering leads navigating AI integration, you must shift your focus from merely automating existing tasks to embracing agentic engineering. This means investing in systems that augment your engineers, not replace them, by building "the thing that builds the thing." Prioritize robust systems design, implement rigorous evaluation frameworks for agent-generated code, and foster a culture that addresses fear of obsolescence, steering your organization towards true innovation rather than just profit margin squeezing.
Key insights
Agentic Engineering shifts focus to building systems that augment humans and master systems design, addressing AI's current organizational value gap.
Principles
- Coding is a small part of software engineering.
- Augment humans, don't eliminate them.
- Master systems design and first principles.
Method
Agentic Engineering involves spec-driven development, rigorous evals, harness engineering, specialized tooling, red-green testing, and modular codebases to build systems that construct other systems, augmenting human engineers.
In practice
- Implement spec-driven development for agent steering.
- Prioritize evals to assess agent-generated code quality.
- Reorganize code for modularity with sub-agents.
Topics
- Agentic Engineering
- AI Productivity
- Systems Design
- Software Quality
- AI Governance
- Developer Trust
Best for: AI Architect, AI Engineer, Software Engineer, Director of AI/ML
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by DeepLearningAI.