• Debian Setup
• AutoBuilder

OpenClaw, Hermes, Poke를 쓰며 느낀 단점들

내가 만약 워크스페이스 에이전트를 만든다면 어떻게 만들까?

메모리

• 육하원칙에 맞게 기억해야하는데, 이걸 잘 못 함
  • 맥락을 종종 헷갈려함
• 메모리 툴을 명시적으로 불러야 함
  • 이는 Hermes에서 많이 완화된 부분

Slack

• 답장을 매번 하려 함. 쓰레드에 달리는 모든 글에 답을 함.
  • 매번 답할 필요는 없음. 필요할 때만 하면 됨.
• 언급하지 않은 메시지는 읽지 않음.
  • 모든 워크스페이스의 변화를 계속 보고 있어야 함, 그리고 기억해야 함

Some tools must choose to be dumbed down. PKM tools are one example.

There is a repeated paradigm in the Tools for Thought Software as a Service market. They are too complicated to use. Calendars, Objects, Comments, Backnotes, Blocks, Tasks, etc, etc, etc...

To pull out the most from these tools, you must first grow some skillfulness in these tools and aggregate enough information over a threshold. For team tools, you must ensure this for every member. If you're choosing a tool based on what features it includes, instead of where it can take you, it's like when you prepare for an exam, you try to make a perfect note instead of actually studying.

To successfully harness the productivity tool, you must flow at one point. Tools and infra fade out, and you only focus on the content. Our brain must outpace the tool; our brain must work more than the tool. Even Notion is too complicated for personal task management.

Based on my experience, tools must have the minimum friction, only having...

• Journal. You write daily notes.
• From there on, highlight keywords by adding double brackets.
• Regularly explore the double-bracketed keywords. Write more details.
• Voila! You realize that things are interrelated in a way you never imagined.

Out of intense complexities, intense simplicities emerge. -- Winston S. Churchill

Supergravity Products