Uploaded April 2026 | Updated September 2026, 3 weeks ago
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
We’re in the middle of another leap in abstraction.
Like compilers, cloud, and containers before it, AI coding agents arrived with hype, fear, and broken assumptions. We gave the monkeys GPUs. Sometimes they output Shakespeare. Other times, they confidently ship code that compiles, passes tests, and still does the wrong thing.
The problem is simple: intent gets lost between what we mean, what we ask for, and what actually runs.
This talk delivers a practical model for software development with AI coding agents built on three equally essential ideas:
The Chasm: the divide between human intent and what is actually expressed to an AI coding agent.
The Context: the shared, explicit, and reusable knowledge an AI coding agent operates within. APIs, conventions, constraints, and domain rules replace guessing.
The Chain: the Intent Integrity Chain. A structured flow of prompt → spec → test → code, at each stage produces a verifiable artifact and is validated externally and grounded in a shared context at every stage.
Together, these form a system where intent survives implementation. Natural language becomes specifications. Specifications become tests. Tests become code. Every step is grounded in a shared context instead of assumptions and is never validated by the same model. This approach is informed by recurring failure patterns observed in real AI agents development workflows: systems passed tests, shipped successfully, yet still failed to meet intent.
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
We’re in the middle of another leap in abstraction.
Like compilers, cloud, and containers before it, AI coding agents arrived with hype, fear, and broken assumptions. We gave the monkeys GPUs. Sometimes they output Shakespeare. Other times, they confidently ship code that compiles, passes tests, and still does the wrong thing.
The problem is simple: intent gets lost between what we mean, what we ask for, and what actually runs.
This talk delivers a practical model for software development with AI coding agents built on three equally essential ideas:
The Chasm: the divide between human intent and what is actually expressed to an AI coding agent.
The Context: the shared, explicit, and reusable knowledge an AI coding agent operates within. APIs, conventions, constraints, and domain rules replace guessing.
The Chain: the Intent Integrity Chain. A structured flow of prompt → spec → test → code, at each stage produces a verifiable artifact and is validated externally and grounded in a shared context at every stage.
Together, these form a system where intent survives implementation. Natural language becomes specifications. Specifications become tests. Tests become code. Every step is grounded in a shared context instead of assumptions and is never validated by the same model. This approach is informed by recurring failure patterns observed in real AI agents development workflows: systems passed tests, shipped successfully, yet still failed to meet intent.










![Are We Ready For The Next Cyber Security Crisis Like Log4Shell? by Soroosh Khodami
AI era is bright, but full of terrors!
In a world where vulnerabilities like Log4Shell, Spring4Shell, and the XZ Backdoor make headlines, securing our software ecosystem has never been more critical. In this session, Soroosh, a hands-on architect with experience working on security platform services for large enterprises like Rabobank, will share practical strategies and best practices for securing the software development process, applicable to both small startups and large organizations.
Key takeaways and questions that will be answered in this session:
[Live Demo] What is a Supply Chain Attack, and how dangerous can it be?
An example of lateral movement that begins with a basic SQL injection attack and escalates to gaining root access to a Kubernetes cluster
Exploring new attack vectors in the AI era and the defense strategies to detect, prevent and mitigate them
Most effective practices to secure your CI/CD process
Practical strategies on how Software Bill of Materials (SBOM) help us prepare for the next Log4Shell crisis?
What does DevSecOps mean, and what is its main objective? Are We Ready For The Next Cyber Security Crisis Like Log4Shell? by Soroosh Khodami](https://i.ytimg.com/vi/z0NnBVMqo64/mqdefault.jpg)