Slides for my talk on Pulling Continuous Delivery inside the agentic loop
Description
Remember when one team would build software, then hand it off to another team to deploy it and get it working in production? I seem to recall we > came up with better ways to deliver software. We even made up cool buzzwords like “DevOps” and “Continuous Delivery.”
Many years later, I see people using LLMs to iterate on building an application and treating production readiness as an afterthought. That might > be fine for demos and personal projects. But if we’re going to use agents to build real, business-critical software, we need to use agents to > make sure the software is fit for purpose. We need to know that the software and its infrastructure performs, scales, recovers when things go > wrong, and stays secure and compliant.
I maintain that continuously ensuring software is production-ready as it’s developed is at least as important when using agents as when we > hand-code it. I’ll talk about how to pull the path to production inside the agentic development flow. And I’ll share why doing this kind of blew up on me the first time, and how I had to adjust my thinking to make it work.
Some of the influences for this talk
Harness engineering for coding agent users, Birgitta Böckeler
Harness engineering beyond skills: Using sensors to keep your coding agent in check, (Video) Birgitta Böckeler, Chris Ford
How I Use AI to Code, Chris Parsons
As we build, so we believe, Adam Jacob
Skills Are Context, and Context Needs Tests, Paul Stack
Credits for photos used in the talk:
- Homa Appliances on Unsplash
- Hyundai Motor Group on Unsplash
- Peter Herrmann on Unsplash
- Kathrine Coonjohn on Unsplash
- Abhinav Bhardwaj on Unsplash (also the image used for this post)
