Jake Van Clief argues that most people don't need to build custom AI agents — they need well-organized folders of markdown files describing who they are, how they like things built, and who their clients/investors are. He contrasts the old approach (databases behind APIs, custom Python connectors, per-task tools, one agent per output format) with giving a single model a minimal "harness" of read/write/search tools plus a readable folder tree, so adding a new capability means adding a folder instead of building a new agent. The second half of the video traces computing history — the Jacquard loom, Ada Lovelace, Descartes, Turing, Claude Shannon, Grace Hopper, compilers, C and Python — to argue that natural language is simply the latest layer of abstraction over machine code, and that structuring your intent in folders is the current step in that lineage.
- The folder method: keep markdown/text files describing how you like things built, who you are, and who your clients or investors are, and the AI reads only the relevant parts when you ask for something.
- The traditional agent approach required a database (SQL, Drive, SharePoint, JSON/YAML) behind an API, custom Python connectors, a separate tool for each output format, and web-scraping plus error handling — and changing "slide deck" to "PDF" meant building a second agent.
- A "harness" is the minimal set of general tools — read files, write files, search the web — that nearly every workflow uses; most leading models already ship with it, so extra agent plumbing is often unnecessary.
- He credits the Unix file-tree philosophy from Ken Thompson and Dennis Ritchie (1969–70) as a 50-year-old fundamental that doesn't stop working just because an AI is the thing navigating it.
- On training a Fortune 500 client's 1,500+ employees with Microsoft Copilot: the PowerPoints were "the worst I have seen an AI make ever" because the model couldn't actually control the software — workarounds involved generating HTML or screenshots and pasting them in.
- Transformers predict the most likely answer, but more context layers shift output toward the most fitting answer; adding your own context folder is how you steer it toward what you consider correct — making the AI a tool rather than something that shapes you.
- Historical thread: Descartes' two tests for a thinking machine (1642), Lovelace's objection that machines can't originate, Turing's reply that nothing is original and that machines can surprise us, and Shannon's separation of meaning from the engineering problem.
- Grace Hopper's compiler was rejected by engineers who said computers could only do arithmetic and that you'd lose control of the code — an objection he points out sounds identical to today's criticism of AI coding.
- Every abstraction layer — binary, assembly, Fortran, C, Python — exists to turn human language into machine action; prompting in English is the newest layer, and folders are a way to standardize the one thing the AI still lacks: your intent.
This is the core cost argument against agent-per-task architecture, stated in the clearest terms in the video.
That's one agent. If I change this word to a PDF document, oh, I don't have a tool for PDFs. So I have to come back over and build a whole new one... Now I have agent one, which builds slide decks and knows about my investors, and agent two that can build PDFs in the same way.
A sharp historical parallel that reframes current skepticism about AI-written code as a repeat of an argument that was already lost once.
I had a working compiler and no one would touch it. They said computers could only ever do arithmetic... It's too unknown. You can't control the code. It's going to make too many errors. You're not thinking about the code anymore. Does that sound familiar?
Because in a world full of cheap answers, questions become valuable, instructions become valuable.
Instead of having to build agents for every process, you're building instructions for each process and letting one AI become what it needs when you need it.
If you don't understand the why, you don't understand how something breaks — and you don't know what you can skip.
Every single time you type the letter K, the letter J into a keyboard, that is hundreds of lines of code being executed. You are living on the top of giants right now.