Videos

IBM Technology. Explains the ingestion side of RAG and agents: preparing PDFs and other files so document structure, tables and layout survive into downstream retrieval. That supports the article's warning that RAG quality and safety begin before embedding, especially when parsing complex business documents.

Propeller Consulting. Discusses governance, operating discipline, workforce adoption and ROI measurement as connected parts of scaling AI beyond experiments. That fits the article's maturity model because adoption is treated as changed work with owners and metrics, not as tool usage or workshop attendance.

World Wide Technology. Connects build-or-buy choices to business outcomes, workload placement, cloud economics, data sovereignty, security, infrastructure readiness and hybrid operating models. That makes it a useful strategic companion for deciding when to buy a tool, extend a platform, build a thin custom layer or own more of the deployment stack.

Paragon. Walks through the production RAG permission problem and compares tool-calling, namespaces, ACL tables and relationship-based permissions. That directly supports the article's core rule: retrieval must only return sources the current user is allowed to see, and source-system permissions cannot be treated as an afterthought.

Arize AI. Explains why production agents fail when the system lacks the right context, evaluation data, tracing and domain expertise. It maps well to the article's failure-mode register because it makes reliability an engineering loop: separate retrieval from reasoning, define expected outcomes, evaluate tool calls, and trace failures before changing models.

IBM Technology. Discusses the uneven "barbell" shape of AI coding performance, architecture ownership, agent orchestration, context limits, open-source versus proprietary tooling and why models can solve hard tasks while still failing ordinary engineering details. That supports the article's rule that tests and human review remain the shipping gate.

Tech Field Day. Shows private AI as layered infrastructure: controlled compute, isolated environments, Kubernetes, inference containers, model governance, self-service provisioning, GPU sharing and monitoring. That maps directly to the article's warning that privacy depends on deployment boundaries, logs, access and operations, not on the word "local."

CX Foundation. Breaks voice agents into the practical pipeline: speech recognition, language model, business-system APIs, text-to-speech and interruption handling. That gives the article's rollout framework a concrete technical foundation before readers choose Twilio, Retell, Vapi, LiveKit or another platform.

GOTO Conferences. Connects the EU AI Act to data quality, MLOps, documentation and post-deployment monitoring. That makes it a good companion for the article's SME governance baseline: the work starts with knowing the system, data, owner, purpose and controls, not with buying a compliance platform.

Y Combinator. The Lightcone hosts work through why vertical AI agents — not horizontal wrappers — are the defensible shape for application-layer companies, with concrete examples and a clear-eyed take on which categories the model providers will eat. That is the anti-moat trap the article warns about, expressed as a positive playbook.

Sequoia Capital. Bret Taylor walks through the shift from per-seat SaaS to outcomes-based pricing — what to anchor on (resolution, CSAT, NPS), why incumbents struggle to follow, and how vertical specialisation creates pricing power. It directly mirrors the article's pricing and margin sections.

Anyscale. Walks through why naive LLM serving wastes 60–80% of GPU memory, how PagedAttention borrows OS-style paging to fix that, and why continuous batching produces the 24× throughput numbers the article uses in its math. After this, the article's "you'll be lucky to hit 50% utilisation" line stops feeling abstract.

OpenAI. OpenAI's own Build Hour on prompt caching — the 1024-token threshold, the prefix-stability requirement, audio caching at 99% discount for realtime, time-to-first-token impacts at long inputs. Useful when you are sizing the engineering effort to actually hit the cache reliably on your production prompts.

Prompt Engineering. Walks through Anthropic's prompt caching against Gemini's context caching with concrete latency-and-cost reductions per use case (long-document chat, few-shot, multi-turn). The breakdown of cache-write surcharge vs. cache-read discount is exactly what the article assumes when it talks about when caching pays off.

LiveOverflow. Walks through the actual defence-in-depth playbook — taint analysis on LLM output, restricting expected output shapes, user isolation, few-shot scaffolds, fine-tuning, temperature 0 for determinism, redundancy for critical paths. It matches the article's defence-stack section almost item for item.

LiveOverflow. Frames prompt injection as a classic injection attack against systems that mix instructions and untrusted data — with a concrete content-moderation example where an attacker frames an innocent user. The mental shift from "the model is the target" to "the application is the target" is exactly the move the article opens with.

Y Combinator. Garry Tan walking through what computer use actually changes for the unautomatable long tail of software — legacy apps, internal portals, anything without an API. The framing here is exactly the article's "browser is the universal interface" argument, with a more business-realistic view of where it pays off first.

Fireship. The clearest short explanation on YouTube of the screenshot–action–screenshot loop, including the honest failure modes (Claude wandering off to look at Yellowstone, token burn, latency per step). Fireship is light on production detail by design — read the article for that — but it leaves you with the right intuition for why these systems are expensive and brittle before you commit one to your stack.

Adam Lucek. A longer implementation pass through the cognitive-science-inspired categories — episodic, semantic, working, procedural — wired into an agent in code. Worth watching after the LangChain conceptual video if you want a more opinionated mental model and a working example to crib from.

LangChain. Short, no-code walkthrough of the short-term-vs-long-term split, the three shapes long-term memory tends to take (instructions, profile, list of objects), and the hot-path-versus-background trade-off for when to write. The article's memory-architecture section assumes exactly this taxonomy.

LangChain. Lance Martin's framework — write, select, compress, isolate — with concrete examples of when to summarise an action history, when to offload state to files, and when to spin up sub-agents purely to protect the parent's context. Maps almost directly onto the article's section on managing 1M-token windows in practice.

Chroma. Kelly Hong walking through Chroma's research on 18 models — why needle-in-haystack scores are misleading, how performance degrades with ambiguity and distractors, why even simple string-repetition tasks degrade past 500 tokens. Short, evidence-based, and exactly the case the article needs you to take seriously before getting to the engineering moves.

aiwithbrandon. The same kind of build, but in CrewAI's role-goal-backstory style — agents as team members, tasks as deliverables, the framework hiding the execution loop. Watch it immediately after the LangGraph course; the contrast in how much the framework decides for you is exactly what the article is asking you to weigh.

freeCodeCamp.org. A long, code-along build through LangGraph's state graphs, nodes, edges, conditional routing, checkpoints, and tool use. By the end you have enough feel for the typed-state, "every transition is explicit" model that the article's comparison to CrewAI and to direct-API code stops being abstract.