[{"content":"I\u0026rsquo;ve saved 7,902 articles.\nMy WeRead is full of highlights. My Cubox sits quietly with clipped web pages. My Zotero is stuffed with English papers I haven\u0026rsquo;t gotten around to reading. On my phone and my computer, browser tabs stretch out in row after row, and WeChat\u0026rsquo;s floating windows and Favorites are full of \u0026ldquo;read later\u0026rdquo; promises I made to myself.\nEvery time I hit save, my brain releases a faint hit of dopamine — as if, just by tucking a link into some corner, the knowledge had already synced itself into my head.\nBut honestly? When I actually need something, I can\u0026rsquo;t find a single one.\nA few days ago I was rushing a draft, halfway through, and I urgently needed a sharp idea I\u0026rsquo;d read before, as evidence for a point. I clearly remembered saving it — I could even vaguely picture the colors of the article\u0026rsquo;s illustration. I eagerly opened my collection, typed in a few keywords from memory, and got dozens of completely irrelevant results. I scrolled down the timeline for a full twenty minutes, eyes glazing over, and still didn\u0026rsquo;t find it.\nIn the end, so I wouldn\u0026rsquo;t miss my deadline, I closed the collection, quietly opened a search engine, Googled it again, and found a decent substitute in three minutes.\nThe moment I closed the page, I looked at the collection icon in the top-right corner of my screen — \u0026ldquo;1000+\u0026rdquo; — and it suddenly felt absurd. And in that instant I understood: these 7,902 articles I saved are barely different from not having saved them at all.\nThey\u0026rsquo;re like the clothes in my closet with the tags still on — bought because \u0026ldquo;I\u0026rsquo;ll wear them someday,\u0026rdquo; left gathering dust in a corner for a year, and when I actually need to go out to dinner, I still feel like I have nothing to wear.\nI used to blame my bad memory, blame myself for being too lazy to regularly \u0026ldquo;clean up\u0026rdquo; and \u0026ldquo;review\u0026rdquo; my collection. But now I finally see it: the problem isn\u0026rsquo;t that I\u0026rsquo;m not diligent enough. My knowledge system was built on the wrong logic from the very start.\nFigure: Saved… read later… and in the end, I just Googled it again. I turned knowledge management into hoarding, and turned the brain — which is meant for thinking — into an inefficient warehouse.\nWe\u0026rsquo;re used to replacing \u0026ldquo;digesting\u0026rdquo; with \u0026ldquo;moving.\u0026rdquo; See a good article, save it on a whim — like hauling bricks into a warehouse, without ever thinking about how to build a wall out of them. Over time the warehouse fills with junk: no index, no categories, until I can\u0026rsquo;t even remember what\u0026rsquo;s in there. And when I actually need to build something, facing that messy mountain of stuff, I don\u0026rsquo;t even have the energy to find a single brick — so I just go buy new ones.\nSaving was never the end of reading — it doesn\u0026rsquo;t even count as the beginning. Information that hasn\u0026rsquo;t been chewed over, reorganized, and expressed by my own brain is just a string of cold characters sitting on a server. It\u0026rsquo;s not my knowledge.\nMaybe starting today, I should stop this self-congratulatory \u0026ldquo;digital hoarding.\u0026rdquo; Instead of piling up 7,902 \u0026ldquo;read later\u0026rdquo; items in my collection, I should start now and write down 10 things I truly understand, in my own words, right now.\nMy Real Numbers Figure: The brain as a warehouse — 7,902 unread, and still nothing to be found. I spent a week counting my own notes.\nMy note system has 621 notes in total:\nInbox: 337 (54%) Areas: 151 Projects: 101 Knowledge: 16 Resources: 3 More than half of it is still sitting in the Inbox. Only 16 have actually become knowledge.\n337 to 16. In other words, for every 21 articles I save, only one becomes knowledge I can actually use.\nI spend the most time collecting and the least time using. This funnel was leaking from the start.\nWhat stings more is that this ratio isn\u0026rsquo;t an accident — the system designed it that way. Saving takes one click. Processing takes 10 minutes. The cheap action gets done the most; the expensive action gets done the least.\nThe Inbox isn\u0026rsquo;t an inbox. It\u0026rsquo;s a graveyard. Once things go in, there\u0026rsquo;s no expiry date, no process — they just keep piling up. When I save things I feel like I\u0026rsquo;m learning, but I\u0026rsquo;m really just moving stuff — from one place to another.\nThe Brain Isn\u0026rsquo;t a Warehouse. It\u0026rsquo;s a CPU. Figure: A warehouse stores things. A CPU computes things. The problem isn\u0026rsquo;t you. It\u0026rsquo;s the process.\nI used to think the problem was that I wasn\u0026rsquo;t disciplined or hardworking enough. I thought if I just tried harder and read a few more saved articles every day, the problem would go away.\nThen I realized: the problem was never me. It was the system.\nA warehouse is for storing things. A CPU is for computing things. Your collection is a warehouse — the more you pile in, the messier it gets. When you save something you think \u0026ldquo;this will be useful later,\u0026rdquo; but \u0026ldquo;later\u0026rdquo; never comes, because you have no process for \u0026ldquo;later.\u0026rdquo;\nThe satisfaction of saving is real. You hit save and feel \u0026ldquo;I\u0026rsquo;ve got this one.\u0026rdquo; But what you\u0026rsquo;ve got is a link, not a piece of knowledge. Saving without a processing step is just piling things up in a different place.\nKnowledge management isn\u0026rsquo;t about being tidy. The measure isn\u0026rsquo;t how much you stored — it\u0026rsquo;s how much you used.\nAfter something comes in, nothing tells you: should this be deleted, stored, or turned into a card? That missing step is called \u0026ldquo;processing.\u0026rdquo; Without processing, your collection is just a bigger, messier warehouse.\nWhy does \u0026ldquo;later\u0026rdquo; never come? Because \u0026ldquo;later\u0026rdquo; has no place in your system. No deadline, no reminder, no fixed time slot. When you save something you think \u0026ldquo;I\u0026rsquo;ll read it when I have time,\u0026rdquo; but \u0026ldquo;having time\u0026rdquo; never happens on its own. Without a process, \u0026ldquo;later\u0026rdquo; is just a word you use to comfort yourself.\n10 Minutes a Day, Just Four Things Figure: 10 minutes a day — delete, store, do, transform. Just 5 articles a day. So I set myself a new rule — just one sentence:\nEverything you take in goes to the Inbox. Processing means just four things. Output is measured in permanent cards. Review is measured in four numbers.\nHow does it work? Ten minutes every evening, just four things:\nDelete: 90% of hot takes and duplicates — delete them directly, no mercy. The test is simple: will I still care about this in a month? If not, delete it. Store: if I might use it later, it goes into a literature note — not a permanent card. A literature note stores \u0026ldquo;what this is and where to find it\u0026rdquo;; a permanent card stores \u0026ldquo;what I think about it.\u0026rdquo; Those are two different things. Don\u0026rsquo;t mix them up. Do: if it\u0026rsquo;s an instruction to act, it goes into a project task — no card of its own. If an article tells you to do something — try a tool, read a doc, change a setting — put it on your task list. Cards hold ideas, not to-dos. Transform: if it sparks an idea, write it as a permanent card. This is the only step that creates a card. Say you read an idea, it reminds you of something else, or you disagree with the author — write that thought down, and that\u0026rsquo;s a card. Process just 5 articles a day, and produce just 3 permanent cards a week. No idea, no card — never force it.\nThese 10 minutes go in the evening. The daytime is for input; the evening is for processing. Open the Inbox, start from the top, pick one of the four — delete, store, do, transform — and stop after 5. No more, no need to be perfect. When you\u0026rsquo;re done, close it.\nThe quota is deliberate. Processing only 5 a day forces you to choose — you can\u0026rsquo;t do them all, so you can only do the best. Producing only 3 cards a week forces you to be picky — not every article deserves to become a card. Out of 35 articles a week, only 3 become cards. That ratio IS the filter.\nThis Episode\u0026rsquo;s 3 Permanent Cards Figure: The quota is deliberate — 5 a day, 3 cards a week. Saving ≠ owning: the satisfaction of saving is not the same as learning. Saving without a process is just piling things up somewhere else. The brain isn\u0026rsquo;t a warehouse. It\u0026rsquo;s a CPU: a warehouse stores things; a CPU computes things. A second brain\u0026rsquo;s value isn\u0026rsquo;t in how much it stores, but in how much gets used. Everything in goes to the Inbox. Processing is just four things. Output is permanent cards: 10 minutes a day, 5 articles processed, 3 permanent cards a week — that\u0026rsquo;s the smallest complete loop. One Small Thing You Can Do Today Open your collection and count: how many items haven\u0026rsquo;t you opened in over 3 months?\nDelete 10 of them. Just 10.\nAfter deleting them, you\u0026rsquo;ll find you\u0026rsquo;ve lost nothing — and you feel a little lighter.\nFigure: For every 21 articles saved, only one becomes knowledge. Next time, I\u0026rsquo;ll show how my Inbox started shrinking from 337 — and what the 15-minute daily loop actually looks like.\nI\u0026rsquo;m Lee Kairos, an engineer building my second brain in public. Methods on Tuesdays, real progress on Fridays.\n","date":"2026-11-17T17:00:00+08:00","image":"/p/episode-01-7902-articles/cover-en.webp","permalink":"/en/p/episode-01-7902-articles/","title":"I Saved 7,902 Articles — So Why Can't I Use a Single One?"},{"content":"Welcome to the new Kairos Lab blog. This is the first test post, here to check that Hugo + Stack renders everything properly: headings, table of contents, code blocks, the cover image, word count, and estimated reading time.\nIf you can see this post, the blog is live.\nWhy Hugo + Stack Hugo is a static site generator written in Go, and its biggest strength is speed: even a thousand posts build in seconds. It needs no database and no server — push the Markdown and it becomes a website.\nStack is a card-style Hugo theme made for blogging, and it ships with:\nResponsive layout that looks good on phones and computers A dark-mode toggle in the top right Local search, archives, categories, and tags Table of contents, reading time, and related-post recommendations Previewing locally and publishing When writing locally, start the preview server first — save a change and it shows up in the browser right away:\n1 2 3 4 # Start the local preview (-D shows drafts too) hugo server -D # Open http://localhost:1313 Once it looks right, push to GitHub and Actions builds and publishes it automatically:\n1 2 3 git add content/post/kairos-blog-test.md git commit -m \u0026#34;Publish test post\u0026#34; git push origin main What a post\u0026rsquo;s front matter looks like Every post starts with front matter — the title, date, categories, and tags:\n1 2 3 4 5 6 7 --- title: \u0026#34;I Saved 1,000 Articles — Why Can\u0026#39;t I Use a Single One?\u0026#34; date: 2026-11-14 categories: [\u0026#34;knowledge-management\u0026#34;] tags: [\u0026#34;Knowledge Management\u0026#34;, \u0026#34;Collecting\u0026#34;, \u0026#34;Inbox\u0026#34;] draft: false --- A post with draft: true is a draft and won\u0026rsquo;t be published; set it to false and it appears on the site.\nWhat\u0026rsquo;s coming next The first real post is already written: \u0026ldquo;I Saved 1,000 Articles — Why Can\u0026rsquo;t I Use a Single One?\u0026rdquo;, built on my own numbers: 621 notes, 337 sitting in the Inbox, and only 16 in the knowledge base.\nOnce this test post confirms the layout is fine, Episode 1 goes out. Stay tuned.\n","date":"2026-11-13T12:00:00+08:00","image":"/p/kairos-blog-test/cover.jpg","permalink":"/en/p/kairos-blog-test/","title":"Test Post: Kairos Lab Blog Is Live"}]