Show Notes
This is a re-release of an episode that originally ran in October 2019.
If you’re trying to manage a project that serves up analytics data for a few very distinct uses, you’d be wise to consider having custom solutions for each use case that are optimized for the needs and constraints of that use cases. You also wouldn’t be YouTube, which found themselves with this problem (gigantic data needs and several very different use cases of what they needed to do with that data) and went a different way: they built one analytics data system to serve them all. Procella, the system they built, is the topic of our episode today: by deconstructing the system, we dig into the four motivating uses of this system, the complexity they had to introduce to service all four uses simultaneously, and the impressive engineering that has to go into building something that “just works.”
More from Linear Digressions
As AI systems grow more powerful, they grow harder to understand — and that tradeoff has never mattered more. Most interpretability tricks give us approximations from the outside, but mechanistic interpretability takes a different approach: cracking open the model itself to trace *why* it behaves the way it does. This episode digs into what makes mechanistic interpretability fundamentally different from other explainability methods, and why it might be the most promising path toward actually understanding what's happening inside modern LLMs.
Labeled data is expensive, slow, and painfully hard to come by — and when you're trying to evaluate whether an AI workflow is actually doing what you want, the problem gets even messier. How do you judge whether a chatbot response was helpful, honest, or hallucination-free at scale? This episode digs into using LLMs as judges: letting the models themselves evaluate the quality of AI outputs, from simple chat exchanges all the way to complex multi-step agent behavior.
Originally aired on the Harvard Data Science Review podcast.