Videos

Google for Developers. The video introduces multilingual text embeddings that can run locally and support semantic search and RAG without sending every document to a hosted API. For Estonian companies, that is a useful technical complement to the article's internal-knowledge-search pattern: multilingual retrieval is valuable only when it also respects data locality, permissions and source authority.

Crowdin. Shashi Bhushan starts with workflow mapping rather than tool selection, then covers source-text quality, human review, AI proofreading, glossary checks, product-team involvement, pilots and privacy constraints. That is almost exactly the operating model the article recommends for Estonian teams working across Estonian, English, Russian, Finnish and customer-specific terminology.

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.

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.

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.

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.

IBM Technology. Tighter focus on the two techniques teams most often confuse. Goes deeper on data freshness, source attribution, and the inference-time speed argument for fine-tuning. Worth watching if you are specifically trying to argue against an unnecessary fine-tune project.

IBM Technology. A clear whiteboard pass through all three techniques with their respective costs — retrieval latency, training compute and catastrophic forgetting, the limits of prompt-only solutions — and the combinations that actually make sense in production. The closing example of a legal AI system using all three is almost exactly the article's "when to combine" argument.

Prompt Engineering. A focused walkthrough of Microsoft's GraphRAG — entity extraction, community summaries, query-focused summarization — set up on a local machine with cost notes. Watch it for the graph-RAG section of the article specifically; the cost discussion is the part most write-ups skip.

Cole Medin. A working agentic-RAG-plus-knowledge-graph build, with the agent deciding when to do vector search, when to hit Neo4j, and when to do both. It's the cleanest demonstration on YouTube of the "agent as the retrieval planner" pattern the article describes, in code you can actually pull down and run.

AI Engineer. Douwe Kiela led the original RAG paper at FAIR and now ships RAG into regulated enterprises. The talk is mostly about what stops working at scale — chunking strategies that don't survive 100k documents, "accuracy is table stakes, inaccuracy is the real problem," and why attribution and observability matter more than the embedding model. Good calibration before re-reading the article's eval and monitoring sections.

AI Engineer. LlamaIndex's CEO walking the gap between "naive RAG demo" and a real pipeline — small-to-big retrieval, sub-question routing, hybrid search, evaluation. The shape of his slides maps almost directly onto the article's pipeline sections; watch first, then re-read the article with his diagrams in your head.

Anthropic. Hannah Moran and Jeremy Hadfield from Applied AI walking through how to phrase tool calls and agent prompts on a real Pokemon-playing agent — when to push behavior into the system prompt versus the tool description, what the model needs to know about each tool's preconditions. Useful immediately after you write your first MCP server and find Claude calling it in unexpected ways.

Anthropic. Anthropic engineers walking through what they actually changed when their multi-agent systems were misusing tools — collapsing endpoints, returning names instead of IDs, leaning on MCPs and Agent Skills instead of stuffing more tools into the system prompt. Maps point-for-point onto the article's checklist for tool descriptions and return-shape design.

AI Engineer. Anthropic's Mahesh Murag walking through MCP's design — why tools, resources, and prompts are separated, how clients negotiate capabilities, what production hosts actually do with the protocol. Watch it after the build to understand the parts of MCP the SDK quietly hides and to calibrate the article's "production-ready" checklist against the spec authors' intent.

Web Dev Simplified. A full, code-along build of both an MCP server and a client in TypeScript — tool definitions, schemas, prompts and resources, stdio transport, inspector debugging. It's the closest video on YouTube to actually doing what the article asks you to do, at a pace where you can pause and follow along in your own editor.

Hamel Husain. Hamel Husain, Eugene Yan, Brian Bischof, Harrison Chase, and Shreya Shankar working through tracing, log analysis, LLM-as-judge, and the workflow around looking at real production data. Sit with it the same way you would a long podcast — it is the single best deep treatment of the article's "look at your traces" thesis on YouTube.

LangChain. A guided tour of an LLM trace, project, and dataset by LangChain's co-founder — token cost, latency, error rate, feedback aggregation, drilling into a single retrieval-step span. It's the closest visual analogue to what the article describes when it talks about "every call is a span" and why structured traces beat print logging.

Stanford Online. Methodical pass through rule-based metrics, LLM-as-judge biases, factuality and agent evaluation, and the failure modes of static benchmarks. Use it as the theory companion to the article's section on choosing what to measure and why most off-the-shelf metrics under-predict real regressions.

Dave Ebbelaar. A working AI engineer walking through his actual eval ladder — assert-style unit tests, reference-free metrics, LLM-as-judge alignment with humans, and the analyze/measure/improve loop. The structure is the closest match on video to the article's argument that evals are a regression-catching system, not a leaderboard.

OpenAI. Walks through `strict: true`, the difference from old JSON mode, refusal handling, and how function calling and response-format schemas compose. Useful precisely because it describes the contract the API gives you, which is what the article's production patterns are built on top of.