The Edge Will Not Be Cloud: Why On-Device Liquid Models Change Agent Architecture
Privacy-sensitive and latency-critical agents should be designed with on-device small models as the primary inference path, not cloud-only fallback, because liquid neural networks can run locally with minimal compute and zero cloud cost; this flips assumptions about privacy, latency, and infrastructure.
AngleChallenge the default cloud-centric agent architecture and argue for edge-first design patterns with cloud fallback only where necessary.
Source video ↗The 89% Failure Rate Is an Architecture Problem, Not a Model Problem
Enterprise AI production failure is primarily an organizational architecture and leadership literacy problem, so agent deployments must budget for governance, process redesign, and change management, not just better models.
AngleUse the 11% production success figure to argue that AI adoption strategies should be treated as organizational transformation programs.
Source video ↗Beyond GPUs: Tensor Processors and the Coming Hardware Pluralism
AI infrastructure strategy should evaluate post-GPU tensor processors and open hardware/software stacks because claimed 5x to 10x cost reductions and simpler programming could reduce vendor lock-in, but ecosystem maturity is the real bottleneck.
AngleCompare GPU lock-in and CUDA maturity against open tensor processor promises, focusing on portability and developer productivity risks.
Source video ↗Quantitative AI Is Not Language AI: Separate Stacks for Scientific R&D
Treating all AI as language model tasks is an architectural mistake; quantitative AI and large quantitative models need different compute, data pipelines, and evaluation methods, while hybrid quantum-GPU infrastructure remains a long-horizon prediction.
AngleSeparate language AI from equation-solving AI and argue for distinct R&D infrastructure and evaluation criteria.
Source video ↗