Loading video...

Video Failed to Load

Go Home

Ken Levine talks about how Ghost Story Games uses Gemini to help with: - summarizing scripts - finding root cause in bug logs - analyzing the player’s telemetry data - building queryable design document database He’s skeptical on the generative side of Al: (1/2)

53,179 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Yes here is my 10 minute breathless rant about why I'm so excited about Notion Workers + Custom Agents... Context: I spent this afternoon building a custom agent to help me manage Shiori (a side project I shipped last weekend). I gave the custom agent everything it needs to understand what's happening in my product (email, log drain, sentry alerts, stripe payments, etc) and to do work on my behalf (access to coding agents). In an afternoon of tinkering, this agent can: - Diagnose bug reports proactively by looking through past email conversations, system logs, and database records - Draft replies to user questions with the correct answer based on past email threads, or help me proactively reach out to churning paid users - Self-construct a database of feature requests with an understanding of who is requesting the feature and how they're using the product today - Answer any question I have about how people use the app and what I should be thinking about next - Initiate Claude Code workflows to open PRs proactively in the background when someone sends a bug report or feature request This custom agent is now my "Side Project Chief of Staff" (I don't really know what a chief of staff does but this sounds right). I didn't write a single line of the worker code because I didn't need to: models are so good that I can link to the Workers readme, yap my desired outcome into a microphone, and I get a super-personal and highly-capable AI agent out the other side. So fucking cool. The future is now! I'm excited to see what everyone makes.

Brian Lovin

181,875 views • 7 months ago

Traditional data pipelines don't work for RAG applications. There are 3 issues with them: ​ 1. Traditional data engineering solutions are optimized to handle structured data. RAG applications rely primarily on unstructured data. ​ 2. The connector ecosystem to load data from unstructured data sources is very immature. ​ 3. Traditional solutions do not offer any way to transform unstructured data into an optimized vector search index. ​ The goal of a RAG Pipeline is to solve these problems. ​ The number one objective is to create a reliable vector search index using factual knowledge and relevant context. This sounds easy, but it's one of the biggest challenges we face when building RAG applications. ​ At a high level, there are four different stages in the architecture of a RAG pipeline: ​ 1. Ingestion: Here is where the pipeline loads the information from the data source. ​ 2. Extraction: Where the pipeline processes the input data and decides how to retrieve the text contained inside them. ​ 3. Transform: Where the pipeline chunks the data and generates document embeddings. ​ 4. Load: Where the pipeline creates a search index in a vector database and loads the document embeddings. ​ There are different rabbit holes at each one of these stages. Here are three of them: ​ 1. Ingesting data once is simple. The hard part is refreshing the vector database whenever the original data source changes. ​ 2. Extracting the content of a plain text document is simple. The hard part is to extract content from complex documents containing tables, images, or cross-references. ​ 3. A simple continual chunking strategy with an overlap is simple. The hard part is to find the optimal strategy for your specific knowledge base and the way you are planning to query it. ​ In the attached video, I'll show you how you can build an enterprise-grade RAG Pipeline that solves every one of the above problems. ​ I'll use Vectorize. They partnered with me on this post. You can use them to build RAG pipelines optimized for accurate context retrieval. ​ ​ If you have a few documents lying around, set up a free account and give it a try.

Santiago

40,627 views • 1 year ago

Most people think Rerun is a visualization tool. In reality, it's a database masquerading as a visualizer. I wanted to showcase this functionality by building a full data pipeline consisting of: ingestion → baseline method → eval → finetuning for SLAM on egocentric data. I'll eventually extend this to the rest of my ego/exo datasets, but I wanted to start with a smaller bunch of datasets first. Rerun allows you to expose your saved .rrd files to a catalog where you store datasets. You can query, filter, and join them like any database using DataFusion under the hood. These are the same .rrd files that are automatically generated whenever you visualize anything in Rerun and decide to save it to disk. I brought in 109 VSLAM-LAB sequences across 14 datasets into the Rerun catalog as an example. These include 7Scenes, Euroc, eth3d, and others. Now I can query them with segment_table, filter_segments, and filter_contents instead of parsing CSVs and YAML files. With a strong set of ground-truth datasets for SLAM, baseline additions become nearly automatic with agents like Opus/Codex. This unification of data and visualization is imo the largest missing part for Physical AI. Visualization becomes a natural byproduct of having your data properly structured and queryable. The catalog API is what makes it a database, not just a viewer. I initially focused on VSLAM-LAB data, but I'll migrate all the egoexo data to this format in the coming days to really show just how useful this is.

Pablo Vela

35,179 views • 4 months ago