Only an Outliner Carried Me Through

The Noise Was Not Sound, It Was Interface

I tried many tools, card-based, document-based, and all the polished rooms in between. The document style was often the hardest for me. I would sit down to think, and drift into margins, typography, formatting, and visual housekeeping. I was supposed to build an argument, yet I kept staring at surface.

Markdown was better than Word, much better, and I say that with gratitude. But better was still not enough. I did not need prettier text. I needed a way to hold only one living piece of thought at a time, finish that piece, then move to the next, and only later assemble the whole.

I Could Walk Only After Breaking the Mountain

In the end, workflow saved me, and the heart of that workflow was an outliner. That is how I finished what I had feared I could never finish.

Not because it felt advanced, but because it was honest. It asked me to hold one layer of complexity at a time. A chapter became nodes. Nodes became child nodes. The giant thing became small enough for one day, one sitting, one honest unit of effort.

A Friend Once Named the Secret

There is another memory I return to often.

I wanted to learn programming since childhood and kept failing at it. Around 2016 and 2017, a friend told me something that changed me: programming is the art of managing complexity.

He explained functions as black boxes. Give input, receive output, do not demand every interior detail before you can move. I felt struck awake.

Outlines and Functions Drink from the Same River

Years later, I saw the kinship clearly. A function lets you keep the contract while hiding the machinery. Outliner Zoom Out does the same for thought. A heading can stand as a promise while details sleep beneath it. Then Zoom In lets you enter one node and ignore the horizon for a while. In both directions, complexity is not denied, only placed at the right distance.

For a mind with a narrow working memory window, this is not a productivity trick. It is oxygen.

The Card Wave Came, I Still Returned to the Tree

In 2021 and 2022, card-based knowledge systems rose again. I used them seriously. flomo, Bear with backlinks, Obsidian with backlinks, all of them gave real value.

Yet I still spent most of my time in Logseq and Roam Research. For managing unruly thoughts, they were closer to how my mind moved.

And still, I was not at peace. They were too engineering-heavy in daily use. Conceptual purity often came at the cost of human usability. I have since thought carefully about why every card system eventually led me back to the tree.

Too many core features hid behind plugins. Too much configuration burden was pushed onto users. Even visual customization, often promised as freedom, could become a long negotiation with CSS.

So I Decided to Build a Boat

So I started building my own software. Not to make a grand universal tool, but to build an external working memory for an ADHD life.

My thinking has a concrete limit. I can hold one thing and lose another in the same breath. I needed a screen where the pieces I must think with can stay visible together, so my brain does not have to carry them all alone.

From day one, I moved my own notes and knowledge into it. I use it while I shape it. I repair it while living inside it. I did not want to draft a perfect theory in advance. I wanted the tool to grow in real weather.

Not a Method, a Way of Staying Afloat

For many people, an outliner is simply one note-taking method among many. For me, it is the language I use to negotiate with complexity and keep agency inside chaos.

I no longer demand to understand everything at once. I ask for one node, then the next. This small, stubborn movement is what pulled me through a thesis, through procrastination, through self-doubt, and back toward my own life.