핵심 요약
AI한테 자료 많다고 다 때려 박으면 대가리 터져서 점점 멍청해진다. 콘텍스트 윈도우가 절반 넘게 차면 답변 퀄리티가 수직 하강하기 때문이다. 해결하려면 책의 목차처럼 '맵 파일'을 만들어서 AI가 필요한 파일만 골라 읽게 시스템을 짜야 한다.
주요 포인트
- 폴더 통째로 AI한테 넘겨봤자 용량만 처먹고 대답은 더 못하게 됨.
- 콘텍스트 윈도우의 50%를 넘기는 순간부터 답변 정확도가 개떡락함.
- 수백 페이지 보고서에서 목차 보고 바로 찾아가듯, AI한테도 목차나 맵 파일이 필수적임.
- 맵 파일 시스템을 구축해두면 AI가 수천 개 파일 중 핵심만 쏙쏙 정확하게 뽑아옴.
- 이 시스템을 만들어 두면 AI 한계를 극복하고 대용량 파일도 가뿐하게 다룰 수 있음.
You've got a folder, or likely a few, full of years of work. And you think pointing AI at it would help. But the more data that you give AI, the worse it gets. If you're new here, I'm Dylan. I run an AI consultancy. And this is a common problem I help people fix. So by the end of this video, you'll have an AI that searches thousands of files and pulls the right ones without skipping what matters or making things up. And the best part is is AI will build the whole thing for you. So, let's get into it. This year is one of the ongoing battles that we tend to fight with AI. If you've watched any of my previous videos, you've likely heard me talk about this. Where the AI has limited space in its head. And the more we fill up the AI's head, the dumber it gets. And the technical term for the AI's head is a context window. So whatever model you're using, GPT, Claude, Gemini, it doesn't matter. They're all limited in how much they can hold in their head. And this visual does a really good job at depicting what's happening. Where on the vertical axis, we have the quality of the answer. On the horizontal axis, we have the number of files we've given the AI. Now once we've filled up the AI's head round past 50%, its intelligence drops like a rock. In our use case, that's going to be the number of files that we feed the AI. So we need to build systems and scaffolding around this weakness, so we can get the most out of AI even when we want it to read hundreds if not thousands of files. And that's what I want to show you in this video. Is that system that we can build around this to get the most out of AI without being hampered by this specific limitation. Now what is this system? It's very straightforward. Similar to how a human would deal with the issue. And it's going to be a table of contents or a map file. And I'll explain what that means in a second. But let's say that I give you a report. Say it's a 500-page report. If that 500-page report doesn't include the table of contents, you're going to be confused on where you need to look to get the information that you need. You're going to have to read the entire thing from front to back to get that information. But if you had a table of contents, you can look at that table of contents, realize that the budget is where you're interested, you can go straight to page 23 and get the information that's necessary. This is what we're going to provide to AI. Because right now, when you give AI hundreds if not thousands of files, you're just hoping that it finds what it needs to. And sometimes it does. But this is a really slow and less accurate approach to getting information from those files. Now, I'm assuming that you're using a desktop agent tool like Cloud Co-worker Codex, which are very good at getting through those files. But even those tools with high-end models struggle once you get past a certain point. And that's why we need this. So, now that we understand that we need a table of contents or a map file, how does this kind of interact with AI? Well, there are three layers AI is going to look at before it gets to the raw information. Because you likely have a folder or many sub folders that have hundreds if not thousands of files, and those that's the raw data, the source files. Well, we're going to put two layers of abstraction in front of that so that AI can easily find what it needs without getting overwhelmed. Quick pause in your regular programming. This video is brought to you by me, as always. Two quick things. First off, below is a 30-day AI Insight series, completely free. You'll get 30 insights in your inbox of how you can apply AI to your business and your work. The second thing is if you'd like to work with me, below are a series of offerings to see if there's a good fit between the two of us. Now, let's get back into the video. The first layer of abstraction is going to be the map file. So, this is going to be a map.md file that AI is going to create for you, and this is going to be our table of contents. And it's going to be extremely minimal because AI is going to look at it every single time you interact with AI. So, in this file, all we're likely going to have are the folder names as well as the file names inside of those sub folders, and maybe one to five words summarizing what's in that file. Because when we ask the AI a question of this huge data set of files, it's going to quickly determine based on our ask which of these are relevant for that ask. Once it's identified the ones that are relevant, it's going to go one layer deeper, not all the way to the source files, but one layer deeper. Reason being is that these source files, they could be hundreds if not thousands of pages long. And if they are, that's still extremely overwhelming for the AI. So, the next layer it's going to go is the summaries, because we're going to have the AI create one page or half page summaries for every single file. And maybe even less. It could be just three to five se