The Video Signal

Topic

DevOps Tooling

All digests tagged DevOps Tooling

Aspire 13: One AppHost, Many Languages, Fewer Headaches? - Chris Ayers - NDC Toronto 2026 thumbnail

· 52:34

Aspire 13: One AppHost, Many Languages, Fewer Headaches? - Chris Ayers - NDC Toronto 2026

Aspire AppHost provides a unified orchestration layer for polyglot systems, allowing developers to treat mixed-stack projects (e.g., .NET API, Python worker, Node front end) as a single product rather than multiple disconnected repositories. The system simplifies local development by automating service wiring, managing configuration via environment variables, and providing a centralized dashboard for unified telemetry, logging, and debugging across diverse languages.

Key takeaways

  1. Unified Polyglot Orchestration 2:00

    Aspire AppHost allows developers to declare services, dependencies, and resources in one place, eliminating the need for scattered configuration files (YAML, appsettings.json) and complex manual setup scripts.

  2. Centralized Observability 3:30

    The dashboard provides a single pane of glass to view telemetry, structured logs, traces, and metrics from all connected services, greatly simplifying debugging across different language stacks.

  3. Automated Service Wiring & Discovery 5:40

    Service discovery is handled automatically using conventions (e.g., `services_` or `connections_`), ensuring that services can find and connect to dependencies (like databases) without manual IP/port configuration.

  4. AI-Assisted Development Workflow 9:40

    New agent capabilities allow developers to manage environments, query logs, debug failures, and even suggest code fixes directly within the chat interface (e.g., using VS Code Copilot).

Watch on YouTube Full article

Wayve's Dave Kirk: Why Agentic Code Review Needs Evals thumbnail

· 23:55

Wayve's Dave Kirk: Why Agentic Code Review Needs Evals

Dave Kirk details Wayve's approach to agentic PR code review, emphasizing that reliable AI adoption requires moving beyond 'vibes-based' evaluation. The system uses a structured feedback loop—integrating sentiment tracking, usage metrics, and dedicated evaluations (Evals)—to improve prompts and guide multi-agent behavior in complex, high-stakes environments like self-driving car development.

Key takeaways

  1. Agent Reliability Requires Observability 2:08

    Multi-agent systems are stochastic and difficult to predict. Kirk notes that observability is critical; if a single agent's behavior cannot be observed, building reliable, production-ready multi-agent workflows is extremely challenging.

  2. The Pitfalls of Public Benchmarks 10:53

    Public coding benchmarks are often untrustworthy because agents can learn to 'cheat' the tests. Performance gains may simply reflect improved cheating mechanisms rather than genuine capability improvements.

  3. Structured Feedback Loops are Essential 22:30

    Wayve implements a feedback loop by collecting data on code review outcomes, including sentiment (thumbs up/down) and usage tracking. This data is used to identify common mistakes in prompts and improve agent behavior iteratively.

  4. The Value of Evals 23:25

    To ensure confidence, the team uses dedicated evaluation agents (Evals) that test the quality of output from other agents. Kirk highlights performing 'eval-driven development,' where the eval mechanism is built before the agent itself.

Watch on YouTube Full article

SEE CMUX SOLVE Multi-Agent Orchestration (Claude Code and Pi Agent) thumbnail

· 30:29

SEE CMUX SOLVE Multi-Agent Orchestration (Claude Code and Pi Agent)

This video explores advanced multi-agent orchestration patterns and the critical need for 'agentic access' to improve agent performance. The speaker argues that simply running many agents in a loop ('vibe coding') is insufficient; true progress requires visibility and programmatic control over the entire process. Cmux is presented as a tool that solves three major problems: lack of programmatic access, inability to monitor/improve agents, and slow manual setup time for large agent teams. The core architectural pattern recommended is three-tier orchestration (Orchestrators prompt Leads, who prompt specialized Experts).

Key takeaways

  1. Agentic Access is Paramount 2:03

    An agent you cannot see or programmatically interact with cannot be improved. This principle distinguishes 'agentic engineering' from simple 'vibe coding.'

  2. Three-Tier Orchestration Pattern 0:45

    The recommended structure for multi-agent teams is: Orchestrators prompt the Leads, and Leads prompt specialized Agent Experts.

  3. Scaling Compute to Scale Impact 6:20

    Multi-agent orchestration allows scaling compute by running multiple diverse agents (e.g., Claude Code, Codex, Pi agent) in parallel on the same problem, ensuring visibility into all attempts.

Watch on YouTube Full article