This week is wholly a story about a person. If the vision declared and Build proved, the third week watches one person actually live out that sentence. It's the week the abstract narrows down to a single person's name.
This Week's Signal
Han Mi-jeong built her own tool. Age 41, middle school Korean-language teacher, 4 classes of 132 students. She doesn't know a single line of code. And yet, in this month's Field piece, she is herself making and using a grading tool. How was it possible? The truly hard 80% of making — what to evaluate and by what standard — had been in her head and at her fingertips for 12 years already. She only had to lay on one axis that moves it onto a screen. A developer didn't make it for her. She made it. The person who knows her own work better than anyone in the world.
From "who will make it for me" to "I make it." This is the most important turning point in the entire month. The person with expertise was always in the client's seat — organizing requirements, handing them to a developer, waiting a long while, receiving the result, and repeating "that's not it." Once the person holding the 80% and the person actually making become the same person, that grueling round trip itself disappears. With no interpreter, there's no mistranslation. This is why Han Mi-jeong's screen resembles her grading method so precisely. No one came between her and the screen.
A small tool is the greatest proof. A single screen for grading 132 students isn't grand. No flashy features, no impressive graphs. But this is the complete proof of the proposition: "a non-specialist, with only her own field's knowledge, makes a tool that fits her exactly." This one small, ordinary case quietly holds up the whole of Vol 3. Big words gain weight only when they stand upon small facts.
Tool · Package Notes
This week's note is about the end of customization as a luxury. In the old world, "a tool that fits me exactly" was an obvious luxury — you had to find someone to make it, pay the cost, and wait out the schedule. So most people put up with "roughly fitting" general-purpose tools, uncomfortable as they were. When the person holding the 80% lays on the final 20% themselves, customization becomes the default rather than the exception. Han Mi-jeong's screen holds only her classes, her items, her grading order. There isn't a single field for another school or someone else's classroom. No excess — that's the mark of a tool you made yourself.
A Short Thought
A good tool resembles the person who made it. The reason a store-bought tool always feels somehow awkward is that it was made by someone who doesn't know me. When the distance between the maker and the user becomes zero, that awkwardness becomes zero too. The reason Han Mi-jeong never once asks "why is this set up this way?" while using her own tool. There's no need to ask. She decided it so.
From the Field
We close this week with a single line from Han Mi-jeong. "At first I wished someone would make a thing like this for me. But once I actually tried it, explaining what I wanted to the person who'd make it turned out to be harder than just making it myself. Moving what's in my head to someone else accurately was the hardest part of all." Since the 80% was inside her, the hand closest to that 80% was, in the end, her own hand too. Once the cost of interpretation vanished, making became part of her daily routine.
This Week's Question · Next Week's Preview
If there's something you've always put off, wishing "someone would make this for me," then for this week at least, seriously weigh the possibility that the "someone" might in fact be you. The labor of making may be smaller than the labor of explaining. Next week, closing March, we'll see how the three threads of the three weeks — person, machine, field — converge into one sentence, and what next month's Vol 4 begins to ask.
makemind.dev "Signal" — once a week, a short summary of the week's Signal.