What Developers Actually Need to Know Right Now
Summary
Addy Osmani, formerly of Chrome's developer experience team and now with Google Cloud AI, discusses the current state and future trajectory of AI in software engineering. He emphasizes that the primary challenge with AI agents is coordination and orchestration, not code generation itself, highlighting frameworks like Google's Agent Development Kit (ADK) and protocols like A2A and MCP. Osmani also addresses the "Something Big Is Happening" debate, cautioning against overstating AI's current production readiness versus its prototyping capabilities. He notes a shift where planning and defining constraints are becoming more critical than coding, and that code review is increasingly complex due to AI-generated pull requests. Despite these challenges, he strongly encourages new entrants into software engineering, viewing the current era as an unprecedented opportunity for innovation. Osmani also advises careful experimentation with token costs and observes that many 2028 AI predictions are already technically feasible, with adoption being the slower factor.
Key takeaway
For AI Architects evaluating agent-based development, you should prioritize robust orchestration and coordination strategies over raw generation capabilities. Focus on defining clear planning phases, establishing precise constraints, and implementing rigorous quality gates for AI-generated code. Your ability to manage agent interactions and ensure traceability will be crucial for successful enterprise-scale deployments, rather than merely deploying numerous agents without oversight.
Key insights
AI's true frontier lies in orchestrating agents to solve real problems with control and traceability.
Principles
- Coordination, not generation, is the hard problem for AI agents.
- Planning is the new coding in an AI-assisted development workflow.
- The gap between AI capability and adoption is where innovation will occur.
Method
Utilize frameworks like Google's Agent Development Kit (ADK) to integrate deterministic workflow agents and dynamic LLM agents, balancing predictability and flexibility for specific tasks.
In practice
- Codify team best practices for agents in Markdown or MCP tools.
- Define clear quality bars for merging AI-generated code.
- Experiment with token costs to assess productivity gains.
Topics
- AI Agents
- Agent Orchestration
- Software Engineering
- LLM Productivity
- AI Adoption
Code references
Best for: AI Architect, Software Engineer, Machine Learning Engineer, AI Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by AI & ML – Radar.