AWS Architect Gili Nahum: Developers Must Evolve Beyond AI Proxies
AWS AI Solutions Architect Gili Nahum argues that developers are becoming 'meat proxies' for AI. Moving toward autonomous 'Software Factories' using tools like Amazon Bedrock, teams can automate coding, security fixes, and PR generation.

The landscape of software development is undergoing a profound paradigm shift, moving away from human-driven coding toward fully autonomous "Software Factories." Speaking at the recent Geektime Code conference, Gili Nahum, AI Solutions Architect at Amazon Web Services (AWS), warned that developers are increasingly at risk of becoming mere "Meat Proxies"—human bottlenecks who spend valuable time approving trivial actions for artificial intelligence agents.
Moving Toward Autonomous Software Factories
According to Nahum, the evolution of coding has accelerated dramatically over the past few years. While developers wrote raw code themselves in 2021 and marveled at simple autocomplete features in 2022, the industry is now entering an era where cloud-based AI agents drive the entire development lifecycle. A modern Software Factory takes raw input—such as a Jira ticket, a Slack alert, or a user interface bug—and outputs thoroughly tested, working software.
In this new framework, human involvement is intentionally minimized to strategic control points known as "gates." Over time, these gates transition from semi-automated checkpoints to fully autonomous decision-making loops. The Large Language Model (LLM) evaluates its own performance, determining whether the output meets strict quality standards before proceeding, and only escalating to a human developer in exceptional edge cases.
Infrastructure and Security in Cloud Agents
For this automated workflow to succeed, organizations must implement structured data flows, advanced edge capabilities, and robust verification systems. On the infrastructure side, tools like Amazon Bedrock Agent Core provide isolated runtime environments and granular permission management. These safeguards ensure that individual agents can run safely for hours while maintaining a strictly limited blast radius.
Furthermore, Agent Core incorporates essential architectural layers such as persistent memory, which allows the system to learn from previous executions, and comprehensive observability features powered by OpenTelemetry (OTEL). These tools grant engineering teams full transparency, enabling them to track which agent modified code at 2 a.m., debug errors efficiently, and monitor token consumption and workflow costs precisely.
Real-World Demonstrations and Future Horizons
To illustrate the velocity of these automated factories, Nahum demonstrated an open-source project called Autonomous Background Coding Agent (ABCA). During the live demonstration, the agent received a request from GitHub, provisioned a secure environment, fetched the corresponding code, and reached a human approval gate in just seven seconds, delivering a fully prepared Pull Request within three minutes.
The competitive advantages of adopting this architecture are substantial. Automated systems can identify and remediate cybersecurity vulnerabilities overnight while developers sleep, delivering a ready-to-review patch by morning. Similarly, feature requests discussed by teams can be conceptualized, developed, and prepared for production deployment almost instantaneously.
Nahum concluded by challenging the audience to reconsider their evolving professional roles, urging developers to transition from traditional intermediaries into "Factory Engineers" who build and manage autonomous systems. As he famously put it: "The next time you type 'Yes' to an agent, ask yourself—how much longer will you remain a proxy?"





