# Meta, Stanford & Odevo on Agentic Coding at Scale

## Executive summary

The session explores scaling agentic coding adoption from a single team to hundreds of engineers. Key findings highlight that while AI tooling can drive massive organic community growth (e.g., Meta reaching 80%+ weekly usage), success is highly dependent on organizational maturity. Speakers warn that deploying agents into an organization with weak software delivery practices will worsen outcomes, emphasizing that foundational improvements—such as robust CI/CD pipelines, dedicated platforms, comprehensive testing, and established coding standards—must precede advanced AI adoption.

## Key takeaways

- Meta's Adoption Strategy: Meta grew an organic community from ad hoc usage to over 40 times its original size. Weekly tool usage increased from under half to above 80%, demonstrating that sustained adoption can be achieved without mandatory enforcement. (00:01:39)
- Performance Spread and the 10x Engineer: Studies across 150,000 engineers show the widest performance spread ever measured. Contrary to initial hypotheses, top performance is now being achieved by individuals skilled in creating and utilizing agents. (00:02:47)
- Prerequisites for Agentic Coding: The 2025 DORA report warns that pointing agents at an organization already struggling with software delivery will make things worse. Successful adoption requires fixing fundamentals first: CI/CD, a platform, tests, and coding standards. (00:05:1)

## Technical details

- AI Adoption Maturity Model: Meta developed a maturity model to guide the spread of successful AI patterns beyond small, siloed groups. (00:01:39)
- Software Delivery Fundamentals: Before adopting agents, organizations must establish reliable processes including a dedicated platform, automated testing capabilities (agents must be able to run tests), and agreed-upon coding standards. (00:05:1)
- Quality Assurance & Planning: Sustainable engineering practices include defining error budgets, setting availability targets, and shifting quality assurance left through spec-driven development rather than relying solely on mandatory code reviews. (00:08:26)

## Practical implications

- Prioritize fixing core build engineering fundamentals (CI/CD, platform stability) before scaling AI tooling.
- Focus on creating 'broken comb' talent profiles—individuals with diverse areas of depth—to thrive in the new age of development.
- Implement sustainable operational practices like defining error budgets and optimizing on-call rotas to prevent burnout.
- Treat AI adoption as a cultural change requiring empathy, rather than just a tooling rollout.

## Topics

Agentic Coding, Software Development Lifecycle (SDLC), CI/CD, Organizational Scaling, DevOps Maturity, AI DevCon NYC 2026

Source: https://www.youtube.com/watch?v=jfTltMo0TMg