A clear record first helps me see myself.
01 Reading notes
Find the gap in understanding before the elegant opening.
Yuanshan enjoyed building projects but struggled to turn them into written summaries. Having seen my technical articles and mind maps, he wanted to know where to begin. In the reply I first brought writing back to a conversation with oneself: sharing is an additional benefit; the first reader is you. A blank document need not immediately face everyone's judgment.
This is especially true of technical writing. A lack of elegant vocabulary may not be the central obstacle. If you cannot explain the problem, the reason for choosing an approach, and where the difficulty lay, searching for an appealing opening will not supply the missing understanding. I would first put those questions on paper and see which I cannot yet answer.
That does not mean I must resolve every technical uncertainty before writing. A draft can contain things I do not know. When I get stuck, I can mark the point and return to the code, consult a source, or repeat a small experiment. Writing then does more than preserve completed understanding: it reveals where understanding remains incomplete.
Once I can explain a decision in my own words, that passage has value even if it is not ready to publish. The next similar problem need not depend entirely on a vague memory. Temporarily setting aside “I must publish a good article” to finish one explanation often makes the first step easier.
you only need to explain the problem and the solution clearly.Open this letter
02 Reading notes
Let the problem shape the structure. Do not squeeze experience into a log.
I offered Yuanshan a rough structure: background and pain points, existing approaches, architecture, implementation, difficulties and the surrounding ecosystem. Its purpose is to order thought, not require every article to fill every category. Explaining one important difference between two approaches can be a useful record on its own.
Writing strictly in the order work happened can leave a sequence of installation, modification and completion while missing the reasons a reader needs. I would return to the moment that changed the approach: what constraint appeared, why was the old solution insufficient, and what did the new one cost? Those turns determine the article's structure.
Then add detail. A setting, a code fragment or a measurement should explain something, rather than merely prove how much work I did. Material unrelated to the central question can remain in personal notes. Leaving it out does not dismiss the effort; it gives this particular explanation a clear boundary.
A mind map need not begin neatly either. In the original reply I distinguished an article's structure from a free-form canvas: the first becomes ordered through understanding, while the second can be drawn freely. Allow branches during exploration and choose the main line during revision. Treating exploratory confusion as an error to correct immediately may prevent the first mark on the page.
03 Reading notes
Make regular records to gain a little observing distance.
Tinglan's message concerns another kind of writing. Recording emotions had helped him begin recognizing himself in retrospect, and he had shared my article with friends. What moved me was less the praise than the way words became somewhere to return: a feeling unclear at the time could still be revisited later.
My reply admitted that busyness had kept me from updating my monthly posts for a while. Recording is not a habit permanently secured once and for all. I needed to find time again, step slightly outside the everyday, and examine that stretch of experience. A regular occasion can keep it from being forever displaced by something more urgent.
I would make the questions specific: what repeatedly takes my energy, which decisions merely follow inertia, and which feeling differed from what I expected? Writing these down does not require an immediate score. Distinguishing what happened from how I interpret it makes room for another explanation.
This can inform technical reflection without becoming the same kind of writing. Technical records may require reproducible steps; a private diary may preserve only a moment and a few words. Different records serve different purposes. Allowing different degrees of completeness helps writing enter actual life, rather than occur only on days fit for publication.
stepping outside everyday life to look at it objectively and calmly, and reflecting on the experiences of the past stretch of timeOpen this letter
04 Reading notes
Return to what you wrote. The perfect tool can wait.
Tinglan recommended a diary app. I said I knew it and added that consciously recording and expressing yourself could help with any tool, even paper and a pen. That reply did not compare features. We were discussing how observation of oneself might happen in life, rather than how to build the most attractive archive.
Revisiting the exchange, I would add the act of returning. Writing something daily preserves material; looking back after a while reveals recurring problems. If a concern appears for several weeks, ask whether one arrangement could change next week, rather than copying the same self-reproach yet again.
Daily and weekly reflections can therefore do different jobs. The daily record holds what happened and tomorrow's intentions; the weekly review places several days together to ask whether the intentions were suitable. It need not demand that every week outperform the last. When exhausted, noticing an overloaded plan and reducing it can also be a useful correction.
What I hope remains is a conversation with myself that can continue. An article can be published later, notes can be unsystematic, and a tool can be ordinary. If writing clarifies one question, or returning to it adds some understanding of my life, the record already has a reason to continue.
Whatever tool you use—even paper and a pen—consciously recording and expressing yourself will have an effect.Open this letter