We close April. The month opened by the single sentence "every server is an app" — having passed through boundary and inviolability — closes on a person's experience.
This Week's Signal
Experience becomes a flow, and a flow becomes a tool. Han Do-gyeong's story, which ran through this whole month, closes here into one picture. What he built is not a clever diagnostic machine. The order of care that became second nature seeing 60 patients a day — he sculpted that flow of experience into a tool. That flow of greeting the patient, asking, tidying the records was originally only in his head. The moment he drew it out as a tool, the same flow became a screen. Just as a server becomes an app, experience becomes a tool. April's proposition came alive and moving in one person's workplace.
Closure builds trust — once more. The reason his tools were accepted by patients and fellow physicians alike was not that they were rich, but that they were clearly closed. The line that diagnosis is a human's job is nailed down by the absence of a tool, so no one worries that "a machine makes the judgment." The third week's "I trust it because parts are closed" was proven, right there in the field.
Vol 4 became one picture. Horizon threw out the proposition ("server = app, non-exposure = boundary"), Build proved it (the black box's absent tool), Field moved it into a person (experience → flow → tool). Read separately, three pieces; gathered across a month, they speak one and the same sentence from three angles — sculpt capability into tools, but decide first what not to sculpt.
Tool & Package Notes
This week's note is the first step in moving experience into a tool. It starts not from grand automation but from recalling one task you do in the same order every time. Write each step of that order as a tool, connect the steps, and leave the steps you must not touch empty. Han Do-gyeong started right there. The flow is already inside you — you only need to draw it out. You don't have to complete it all at once. Pull one step out as a tool, and if it fits your hand, move on to the next. The flow grows one line at a time.
A Short Thought
The experience of someone who has done something for a long time usually stays as tacit knowledge. It can't be fully put into words; you learn it by watching from beside them. But if that experience holds a consistent flow, the flow can become a tool. The moment it becomes a tool, tacit knowledge turns into something shareable. As April ends, the biggest signal left behind is this — at the far end of "the cost of making has dropped" stands the experienced person makes it themselves. Until now, translation was needed between the developer and the field expert. A long bridge of writing down requirements and converting them back into code. The shorter that bridge gets, the smaller the mismatch between what was made and what was wanted.
From the Field
Finally, a word from Han Do-gyeong. "I don't know how to write code. But the order in which I see my patients, I know better than anyone. I wrote that order down as a tool, and it became a screen." Even without being a professional developer, the person who knows the flow of their own work best makes it — this is where this month has arrived.
This Week's Question · Next Month's Preview
If there's something you do in the same order every time, write that order out step by step. That's the rough sketch of the first tool the May version of you will make. Next month (May) we move into what "weaving tools" actually looks like — the sense of combination that joins several tools into one flow. If April drew the boundary, May connects within it.
makemind.dev "Signal" — one breath each week, gathering a week's Signal.