If the screen lives on the server and flows as a definition, the question that remains is the person — so who makes it? This week's answer is both unexpected and obvious.
This Week's Signal
"You don't have to be an expert to make it" is this week's core. The real meaning of leaving compilation behind comes into focus in the third week. When the wall of building disappears, making doesn't get faster — it gets wider. Since no baking process is needed, it's no longer the work only of those equipped with a toolchain. Anyone who can handle a definition can make. Into that "anyone" step both an engineer handling chips and a farmer in a greenhouse, side by side.
"On the Chip" gave back "the engineer's time." When the time once spent separately developing a dedicated GUI disappears, the engineer spends that time on capability instead. The screen goes on quickly as a definition, and the genuinely hard parts — sensors and control logic — get the focus. Lighten the screen labor, add it to the essence — that's the practical gain "leaving behind" delivers.
A field tool went from "someone else's" to "mine." Jeong Bok-san's notebook became this week's emblem. From a person who uses someone else's app, to a person who makes his own tool. That single step from consumer to author is the scene this compilation-shedding month wanted to show. He didn't learn to code. It's just that, since the screen lives as a definition, he can directly touch up the fields he doesn't like — and that small bit of authority turns a person into an author.
Tool & Package Notes
This week's note is about the rhythm of fixing as you use. When a tool lives as a definition, you fix it on the spot, mid-use. "I want to move this field's position" — and without waiting for a build, you fix the definition and point again. The line between making and using blurs — you make while using, use while making. The tool grows together with its user. In the baking model, once finished, that's the end; in the definition model, there is no finished. Today's screen fits your own hand a little better than yesterday's — refining one field a day is the normal state.
A Brief Thought
"Anyone makes it" doesn't mean everyone becomes a developer. It means the threshold of making drops, so the person who knows their own work best can directly touch up their own tool. The one who knows tomatoes best is the farmer, not the developer. Returning the tool to that person's hand — that's where this month's weight lies.
From the Field
Jeong Bok-san's three fields became five this week. "Disease memo" and "yield" were added. But what he was prouder of was the field he erased. "The watering time is the same anyway, so I cut it and decided to just record the amount instead." A decision to take away rather than add. A judgment only someone who fixes their own tool can make. In someone else's app, he didn't even have the authority to erase a field. He said he turns this notebook on every day as he makes his rounds of the 8 bays. "Maybe because I made it myself, if I don't write in it, I feel like I'm being lazy." Becoming the owner of a tool also means taking on its responsibility.
This Week's Question · Next Week's Preview
In your work, where is the part you know best? Isn't someone else making the tool for that part? Next week, as it closes out February, "Leaving Compilation Behind" sums up the place it leaves behind, and we see how far Jeong Bok-san's notebook has come in a month — and get an early look at the threshold of March.
makemind.dev "Signal" — February, Week 3. Asking who the maker is.