ReadTube
Back to JetBrains

Scaling AI Without Losing Control

JetBrainsApril 7, 202643m
Topics39
Introduction and Context0:09Evolution from Engineer to Engineering Manager1:31AI Adoption Gap in Enterprise2:01AI Agents as Junior Engineers2:30The Hallucination and Slop Phase3:01Maturity Evolution Timeline3:31Current Adoption Status at Uber4:30Payments, Trust, and AI Autonomy5:31Agent E-commerce Trend6:30Human-in-the-Loop as Guardrail7:00The Cognitive Load Problem7:30Bounded Context as Optimization Strategy8:30Ensuring Architectural Correctness and Security9:00Shift from Creating to Verifying Systems9:31Ownership Principle10:32Framework Migrations and Agent Utility11:31Agent Solutions for Migration Challenges12:31Validation Concerns with Agent-Written Tests13:30Managing Hallucinations14:00The 80% Trust Trap15:01Observability Tooling Requirements15:30The 80-100% Success Definition16:00Enterprise Context and Zero-to-80 Value17:01Core Skills for AI-Augmented Engineering18:01Chain LLMs and Connected Agent Brains18:30Multi-Agent Architecture for Complex Problems19:00SLMs vs LLMs for Reduced Hallucination20:31Tooling Adoption and Experimentation Patterns21:00Bounded Flexibility in Tool Selection22:31Tool Selection and Optimization Strategy23:19Security Considerations with AI Agents25:01Enterprise Observability and Governance26:00Tool Sprawl and Shadow AI Challenges28:01Developer Productivity Metrics in AI Era30:30Developer Experience vs. Productivity32:31Evolution of Developer Roles34:00WebAssembly and Rust Relevance36:31Engineering Leadership in AI Transformation39:33Enterprise Security and Compliance Context42:31
In a Nutshell

AI agents boost productivity but require strict human oversight—especially in high-trust domains like payments—because hallucinations and unchecked code volume quickly overwhelm senior engineers. Success hinges on bounded context, layered agent architectures, and shifting focus from “what agents create” to “what humans verify.” Organizations that master the 80–95 % accuracy gap and enforce observability, governance, and outcome-based metrics will gain the decisive edge.

AI-Generated Notes

These notes were generated by AI and may contain inaccuracies.

Misha Blinkin, VP of business development at JetBrains, hosts a pre-recorded webinar series featuring technology and engineering leaders discussing AI software development trends. The webinar includes live Q&A during broadcast.

Sendhil from Uber joins as an engineering leader and author of the book "Practical WebAssembly." He works on payments infrastructure, building the rails that handle payments to and from Uber globally.

Sendhil transitioned from full stack engineer to engineering manager after experiencing the satisfaction of helping an engineer on his team achieve a senior promotion. This led him to recognize that management was the right career path for him.

According to JetBrains' developer ecosystem survey of tens of thousands of engineering leaders and developers globally, while many developers are adopting AI, only 14% of AI adoption leads to excessive adoption in enterprise settings where measurable value is realized.

Sendhil views AI agents as junior engineers joining the team, enhancing productivity and agility. Current use cases include writing code, writing tests, authoring code reviews, and writing documentation. Documentation quality has improved significantly through AI adoption.

Initial AI adoption involves significant time investment to understand capabilities, educate the system, and provide context. During this period, organizations experience high rates of hallucinations and slop generation, increasing frustration for both engineers and leaders. Once through this phase, AI adoption improves company and team agility.

Sign in to read the full notes

Get access to AI-generated notes, topic timestamps, and more.