The Video Signal

Topic

Continuous Integration/Delivery (CI/CD)

All digests tagged Continuous Integration/Delivery (CI/CD)

· 33:28

Stephane Jourdan, Simon Rohrer & Pini Reznik - From Pipelines to Prompts: Surviving the Shift to AI

This panel discusses the seismic shift from traditional DevOps and Cloud-native practices to AI-native development. Speakers emphasize that while AI agents offer unprecedented speed in coding and diagnosing production issues (24/7), this acceleration introduces significant risks regarding code quality, system context loss, and maintainability. The consensus is that robust guardrails—such as advanced observability stacks, deterministic linting, and disciplined harness engineering—are more critical than ever to manage the complexity of AI-driven deployments.

Key takeaways

  1. AI Shift Magnitude 5:25

    The move to AI is described as potentially 10x or 100x more dramatic than the Cloud shift, impacting not just development teams but every department in an organization. The speed of change requires organizational-wide adoption of AI tools.

  2. Production Agents and Context 8:30

    AI agents are rapidly deploying fixes and features (sometimes 24 hours a day). This necessitates proactive context management, deep observability stacks (e.g., combining Elastic logs with Service Now incident reports), and knowledge of service relationships to manage the 'blast radius' of changes.

  3. Code Quality Guardrails 13:40

    The agents write code that is productive but often poor quality. Speakers strongly advise maintaining rigorous basics like linting and determinism, noting that relying solely on LLMs for perfect output is dangerous.

  4. Continuous Improvement Discipline 22:50

    The core principle of Continuous Integration/Delivery (CI/CD) must be maintained. Advanced teams are implementing self-reflecting agents that learn from both problems and solutions, treating failure feedback as a mechanism for continuous improvement.

Watch on YouTube Full article

· 32:05

Dave Farley - Vibe Coding - Is this really the best we can do? - AI Native DevCon June 2026

The talk argues that while AI represents a massive paradigm shift in software development, relying solely on natural language or current agentic coding practices is insufficient for building complex systems. The core message is that the industry must evolve from being 'solution-focused' to 'specification-focused.' Future programming requires defining desired behaviors using precise Domain Specific Languages (DSLs) and executable specifications (like BDD), ensuring verification at every incremental step.

Key takeaways

  1. The Limitations of Natural Language 12:10

    Natural language is inherently vague, open to misinterpretation, and lacks the simple, consistent grammar required for precise machine execution. It cannot reliably define goals or guarantee deterministic results, making it unsuitable as a primary development tool.

  2. The Role of Specification over Solution 17:25

    Programming languages should be viewed not just as tools to encode algorithms (the solution), but primarily as mechanisms to organize and communicate a precise description of the problem itself. The future program must be an executable specification of what is desired, rather than merely the code that achieves it.

  3. The Necessity of Incremental Verification 23:55

    To manage the speed and scale of AI-generated code (e.g., 12,000 lines/day), development must maintain its core engineering principles: working incrementally, treating changes as experiments, and rigorously verifying every step using continuous delivery practices.

Watch on YouTube Full article