u/zmassisnotnull

I found myself deep in thought as I read through the insightful comments you shared regarding the pressure I felt when looking at my 100 cards.

At first, looking at those 100 cards, I mistakenly believed that the final output could only be achieved if every single card fit together perfectly. I focused on the individual pieces in every way I could

However, I eventually realized that the process doesn’t have to wait until every piece is perfectly aligned. The process itself—doing my best within the allotted time and confidently producing a result—is far more important than the final output itself

If I wait until the cards are perfectly organized, won’t I end up unable to create even a single result?

Written with the help of Google Translate

I found myself deep in thought as I read through the insightful comments you shared regarding the pressure I felt when looking at my 100 cards. The most important realization I gained from those comments is that I often lack sufficient insight.

At first, looking at those 100 cards, I mistakenly believed that the final output could only be achieved if every single card fit together perfectly. I focused on the individual pieces in every way I could.

However, I eventually realized that the process doesn’t have to wait until every piece is perfectly aligned. The process itself—doing my best within the allotted time and confidently producing a result—is far more important than the final output itself.

If I wait until the cards are perfectly organized, won’t I end up unable to create even a single result?

Written with the help of Google Translate.

I’ve mentioned before that I use Post-it notes in my projects. Confidently, I began writing down ideas—one per card. In a short span of time, I had generated dozens of cards, effectively clearing my mind. Yet, looking at nearly a hundred cards that had not yet been connected, I began to feel a subtle sense of pressure.

I completed the "collection" phase—the act of emptying my mind—quickly, finding it truly refreshing. I strive to build a larger picture by starting with small, manageable connections. While I don’t succeed every time, there are moments when a sudden insight flashes—a truly thrilling, dizzying experience.

It got me wondering: what methods do you use to connect those initial fragments of thought?

Written with the help of Google Translate.

Once again, I find myself caught in a cycle of organizing.

I opened an app intending to jot down a brief thought. Forty minutes later, without having written a single word, I was busy creating new tags, rearranging directories, and tweaking naming conventions.

Was this productive? In reality, I accomplished nothing.

I collect knowledge compulsively—gathering it because I need it, because I might need it, or because I anticipate needing it in the future. I even feel a sense of relief looking at the knowledge packed tightly into my storage. I then go through the items one by one, performing "meta-work"—the kind of organizing essential for retrieving and using information later.

The act of organizing even provides a sense of accomplishment. Yet, I am merely organizing so that I can find things later—failing to realize that my future self will likely need something different from what I need right now.

At this point, the effort required to maintain this knowledge has come to outweigh the actual value it provides.

What strategies do you use to avoid falling into the trap of organizing for the sake of organizing?

Written with the help of Google Translate.

Once again, I find myself caught in a cycle of organizing.

I opened an app intending to jot down a brief thought. Forty minutes later, without having written a single word, I was busy creating new tags, rearranging directories, and tweaking naming conventions.

Was this productive? In reality, I accomplished nothing.

I collect knowledge compulsively—gathering it because I need it, because I might need it, or because I anticipate needing it in the future. I even feel a sense of relief looking at the knowledge packed tightly into my storage. I then go through the items one by one, performing "meta-work"—the kind of organizing essential for retrieving and using information later.

The act of organizing even provides a sense of accomplishment. Yet, I am merely organizing so that I can find things later—failing to realize that my future self will likely need something different from what I need right now.

At this point, the effort required to maintain this knowledge has come to outweigh the actual value it provides.

What strategies do you use to avoid falling into the trap of organizing for the sake of organizing?

Written with the help of Google Translate.

Three posts ago I asked why I couldn't find anything in my 4,200 bookmarks. The comments here gave me more than I expected.

This is what I took from them.

Tags describe what something is. But when you need something six months later, you're not searching for what it is — you're searching for the problem you have right now.

Problems repeat. Content is unique.

The CSS trick you saved last Tuesday and the one you need today aren't the same article. But they're the same struggle. Tags won't connect them. The problem will.

That's the gap I kept hitting. Not retrieval. Not organization. The system was waiting for me to remember the old problem. But I only ever knew the new one.

So I stopped trying to tag content and started watching behavior instead.

Every time you copy something, you're describing a problem you're trying to solve. Do it enough times and the pattern tells you more than any tag you'd assign in the moment.

Still early. Still testing.

But if problems come back — and they do — then the archive isn't a graveyard. It's just waiting for the right moment.

Thanks to everyone who commented on the previous posts. This one wouldn't exist without you.

A few days ago I posted about having 4,200 bookmarks I couldn't find. This is what I've been thinking since.

First — I owe this community an apology.

My previous post got called out for sounding like AI. It was. I'm a Korean designer and my English isn't good enough for this kind of conversation. I used AI to write. The thoughts were mine. The words weren't. I'm sorry.

This time I'm writing in my own language for the parts that matter most.

I read every single comment on that post.

GTD. Obsidian. Raindrop. Tags. Zotero. One sentence about why you saved it. Selective saving. Morning review cadence.

Good advice. All of it.

But I noticed something. Every solution puts the work back on the user.

"Be more disciplined." "Build better habits." "Organize before you save." "Review every morning."

I tried all of these. For years. The result was always the same. Excitement → discipline → abandonment.

Here's where I think differently. I'll say it in Korean first, then translate — because I want you to see where the meaning shifts.

[한국어 — 원문]

자동화란 지극히 자연스러운 행동 수집에서 시작할 수밖에 없습니다.

작은 차이가 큰 결론의 차이를 가져올 수 있기 때문이고, 사용자 스스로가 가진 행동 패턴이 결과에 영향을 미치기 때문입니다. 그래서 사소한 것도 놓쳐서는 안 된다고 생각합니다.

물론 눈으로만 보고 끝날 경우 아무런 정보도 얻을 수 없습니다. 하지만 사람이라면 반드시 중요하다 느끼면 수집한다는 특성이 있기에 예외가 적습니다.

무엇이 중요한지는 스스로 '결정'하는 게 아닙니다. 시간의 흐름과 '반복'을 통해 천천히 '발견'하는 것이죠.

매주 나도 모르게 같은 주제를 계속 저장하고 있다면, 그 쌓인 행동의 패턴이야말로 순간의 기분으로 붙여둔 태그보다 내 관심사를 훨씬 더 정확하게 보여주는 셈입니다.

시스템이 나에게 자꾸 정리를 요구하며 신경 쓰게 만들 게 아니라, 내가 어디에 계속 머무르는지 가만히 지켜보다가 — 내가 스스로 깨닫기도 전에 먼저 알아채고 자연스럽게 보여줘야 합니다.

[English — AI translated]

Automation has to start from the most natural behavior — collection itself.

Small differences in what you capture lead to very different conclusions, because your own behavioral patterns shape the outcome. Nothing should be overlooked.

If you only look at something and move on, no information is gained. But people have a tendency to collect what they feel matters — which means the exceptions are rare.

You don't decide what matters. You discover it — slowly, over time, through repetition.

If I keep saving things about the same topic week after week without realizing it, that accumulated pattern reveals my interests far more accurately than any tag attached in a fleeting moment.

Instead of the system constantly demanding that I organize and making me worry, it should quietly observe where I linger — noticing it before I even realize it myself — and naturally surface it.

Not "save smarter." Not "organize better."

Just: let repetition be the filter.

Zero decisions at capture. The system watches the pattern. When something becomes relevant again, it surfaces on its own — before you go looking.

"Notice before I do."

I know this sounds passive. But I've watched too many well-designed systems collapse under their own maintenance cost.

The previous thread taught me something else too: repetition alone isn't enough. The trigger has to be context, not a schedule. Surfacing something "because a date arrived" is different from surfacing it "because you're in the middle of the thing it relates to."

That second one is the hard problem. And the only one worth solving.

It's still rough. I don't know if the theory holds.

But I wanted to share it with people who think seriously about this problem — and find out where it breaks.

Brutal feedback welcome. 🙏

P.S. To everyone who called out the AI writing last time — you were right.

이게 제 진짜 목소리입니다. This is what I actually sound like.

(Translation errors are probably in there. Feel free to point them out.)

안녕하세요~

대단하신 분들이 많아서 좀 부끄럽습니다. 개인 프로젝트로 리버시(오델로) 실시간 대전 서비스 Reversi FL!P를 만들고 있습니다.

[만든 이유] 사실 최종 목표는 실물 오델로 게임기예요. 화면 없이 LED 컬러만으로 대국이 완결되게 만들고 싶었어요 — 누구 턴인지, 어디에 둘지, 누가 이겼는지까지 전부 패드 위에서 끝나는 거죠. 대신 랭크전이나 대전 기록처럼 '온라인' 영역은 폰이 맡아야 해서, 그 인프라부터 먼저 만들었습니다.

[기술적으로는]

• Cloudflare Workers 기반 (D1, R2, Queues, AI Gateway)
• 서버리스로 실시간 매칭/대전 로직 처리
• 초대 코드로 친구랑 바로 대전 가능

[혼자 오셔도 괜찮아요] AI 연습실이 따로 있고, 대전실에서 상대를 기다리는 동안에도 AI와 바로 대전할 수 있어서 상대 없이도 편하게 둘러보실 수 있어요.

[다음 계획] 게임기 쪽은 아직 컨셉 단계라 자세히 보여드리긴 이르지만, 온라인 인프라는 이미 돌아가고 있으니 먼저 플레이해보실 수 있어요. 게임기 진행 상황도 나중에 따로 공유드릴게요.

링크: https://reversiflip.com

플레이해보시고 버그나 UX 관련 피드백 주시면 정말 감사하겠습니다. 🙏

I've been a designer for 25+ years. I'm obsessed with organizing visual structures for a living.

And yet.

I currently have 4,200+ Chrome bookmarks, a Notion database I haven't opened in 4 months, and a "Read Later" folder with 340 articles I will never read.

Last Tuesday I found a brilliant CSS technique. Saved it. Tagged it. Felt good about myself.

This Monday I needed it. Spent 22 minutes searching. Gave up and Googled it fresh.

Here's what I've tried:

• Chrome bookmarks → becomes a cemetery after week 2
• Notion → beautiful to set up, painful to maintain, impossible to search under pressure
• Obsidian → powerful but I spend more time building the system than using it
• Raindrop / Pocket → same graveyard, different UI

Every tool I try follows the same arc: excitement → discipline → abandonment.

I'm starting to think the problem isn't the tools. It's the capture-to-retrieval gap.

We're optimized for saving. But the moment we actually need something, the system collapses.

Genuinely curious:

• Has anyone actually solved this? Not just "managed" it.
• What does your retrieval workflow actually look like on a busy day?
• Is there a tool or habit that made re-finding things feel effortless?

Not looking for another app recommendation — just want to understand how people who've cracked this actually think about it.