# Netlify's Dana Lawson: 'We Ain't Precious No More'

## Executive summary

The landscape of software development is shifting from developer-centric to builder-centric, driven by AI agents. While agents enable non-technical users (Product Managers, designers) to open pull requests (PRs) and build applications, this transition introduces new challenges. Agents can fail by missing crucial product or design context, even when passing automated CI checks. Successful adoption requires platforms to be designed for these diverse 'builders' and necessitates that Product Managers evolve into 'agent orchestrators' who define the system's boundaries and ensure proper human control planes.

## Key takeaways

- Agent Failure Due to Context Loss: An agent, despite having access to skills, CI requirements, and passing automated checks, can fail by using a generic component (e.g., a generic React button) instead of a specific, context-aware component that holds critical requirements like accessibility patterns. (Marc Sloan, 00:00:24)
- Non-Technical PR Merge Metrics: Across hundreds of organizations, 74% of PRs opened by non-technical individuals get merged, and 84% of those merge without any developer needing to push follow-up commits. (Tammuz Dubnov, 00:03:26)
- The Builder Persona Shift: The platform is no longer built solely for developers. The rise of agents means that anyone—therapists, students, small business owners—can build, making the builder persona far broader. (Dana Lawson, 00:05:41)

## Technical details

- Agent Orchestration and Governance: Product Managers must transition from basic workflow definition to becoming 'agent orchestrators.' This requires systems that learn the product's specific domain knowledge and define a clear 'human agent control plane' to ensure checks and balances between agents and PMs. (Emma Burrows, 00:07:43)
- AI-Native Development Tools: Tools like Claude Code, Cursor, Bolt, and Lovable allow anyone with an idea to create working software through conversational intent, treating English as a powerful programming language. (Dana Lawson, 00:05:41)
- Measuring Non-Technical Contributions: Key metrics for assessing non-technical contributions include the count of PRs opened by non-technical individuals and the percentage that merge without developer intervention (aiming for high efficiency to prevent 'PR fatigue'). (Tammuz Dubnov, 00:03:26)

## Practical implications

- Build teams must implement governance layers that validate product context and specific component requirements, rather than relying solely on automated CI checks.
- Platform design must anticipate and serve a diverse range of 'builders' (non-developers) to maximize adoption.
- Product management roles need to formalize the process of defining and automating workflows, moving toward system orchestration rather than manual task breakdown.

## Topics

AI Agents, Build Engineering, Product Management, DevOps, GitHub, Agent Orchestration, Tessl, Autonomy AI, Netlify, Rezonant, Claude Code, Cursor

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