Connecting a Kafka topic to a database sounds like a bounded development task. In production, that connection also involves service and connector versions, encryption, secrets, Kubernetes settings, access permissions and observability. A change that looks correct in the code can affect another part of the system. That web of relationships is the problem Assaf Sauer identifies when asked what still stands between AI-assisted coding and fully autonomous software delivery.
Sauer, founder and CTO of Stacktic.io, joins Alan Shimel to examine the gap between generating an application and operating it safely. His argument is that automation needs a persistent understanding of how components fit together, not just a plausible answer to the latest request. Dependency mapping makes it possible to assess the downstream effects of a proposed change. Without that context, teams still have to determine whether the generated work is compatible with the surrounding infrastructure and its operational requirements.
He describes a framework between the repository and production that stores those relationships and exposes them to AI clients through MCP. People and agents can inspect application topology, missing configuration and validation status before changes ship. Security is part of that assessment: a connector update or configuration change can affect mTLS, secrets, role-based access and requirements associated with PCI DSS or HIPAA. Sauer presents these checks as a way to keep the wider system in view, rather than evaluate generated code in isolation.
The same dependency and validation process should apply regardless of which coding assistant a developer chooses, Sauer argues. He discusses connecting different AI clients to a shared platform and packaging stacks for deployment across clouds, on-premises systems and air-gapped environments. Those examples place the emphasis on continuity between development and operations. Faster code generation is useful, but handing over more of the delivery process requires a reliable account of what the application depends on and what each change will affect.
Alan Shimel is founder, CEO and editor-in-chief of Techstrong Group, a Futurum company, and a member of Futurum's executive leadership team. A technology entrepreneur, media executive and industry commentator, Shimel has spent more than three decades building businesses, communities and media platforms serving enterprise technology professionals, including co-founding StillSecure, a network security company, and the DevOps Institute, a DevOps certification and training body. At Techstrong, he leads a portfolio of media brands including devopsy.kinsta.cloud, Security Boulevard, Cloud Native Now, Techstrong AI, Techstrong IT, Digital CxO, Platform Engineering, Techstrong Semi and Techstrong TV, along with a growing portfolio of events, educational programs and digital communities. With more than 25 years of experience in cybersecurity, Shimel is a familiar voice in the space and was an early advocate of the DevOps movement, helping bring DevOps practices into mainstream enterprise technology. His work today spans cybersecurity, DevOps, cloud-native technologies, artificial intelligence, semiconductors and digital transformation, and he hosts popular programs including Techstrong Gang, Shimmy Says and Still Cyber, After All These Years. He holds a Bachelor of Arts in Government and Politics from St. John's University and a Juris Doctor from New York Law School.