Field

In 2026-04 we ran a piece about a doctor building a clinic flow tool. That piece stated in prose what the tool does not do. This time we drew it in code — this server has no tool that produces a judgement, and it throws if it tries to emit a word that sounds like a verdict.

In 2026-03 we ran a piece about a teacher building a grading tool. That piece never said what the tool based its marks on. This time we built it — every mark comes out carrying which branch of the rubric produced it, and "they slip on question three" is counted out of the papers.

In 2026-04 we ran a piece about a farmer moving thirty years of handwritten notebooks onto one screen. At the heart of that piece — "say it and it becomes a screen" — there was nothing real. We constructed the situation to its real shape and built the whole thing ourselves — and "eighteen days" appears nowhere in the source. It is computed from the records.

In 2026-01 we ran a piece about a non-developer building a club dues tool on a weekend afternoon. That piece had no screen, no definition, no process. This time we built it, and counted how many lines the maker actually touches — forty-five. And if that number grows, the verification fails.

A solo practice with 180 clients. Tax accountant Yun Jae-seong never learned to code. And yet every morning, "Today's Deadlines" appears on his tablet. The screen that reads receipts, builds a history for each client, surfaces what's urgent, and drafts the notices — he built it himself. Without a single line of code.

Collecting materials, organizing, building tables, reviewing, sending out — work that four or five people used to split. Now Han Ji-yeon, a project manager at a translation company, holds that whole flow alone. Not because she cut staff — but because her own tool extended her own hands. A tool does not replace the expert. It sends those hands farther. The final piece, six months from launch.

On a hillside field in Bonghwa, the forty years of farming notes Han Seok-gyu kept had stopped — frozen in faint pencil. When his son Do-jin moved those forty-two notebooks into a single shape, the experience that had stopped began to grow again. And the grandson, who grew up taking that screen for granted, came to foresee days in advance what his grandfather had known only as the air of a spring morning — the story of one family's notebook growing across three generations.

Sixty patients a day, half of them chronic-disease follow-ups. Family-medicine clinic director Han Do-gyeong doesn't know how to code. Yet on the monitor in his exam room, each patient's "past flow" appears on a single screen. What to ask first, what's dangerous to miss — he moved that flow onto a screen himself. But the one tool he deliberately did not build was diagnosis.

Four classes, 132 students, performance-assessment answers piling up week after week. Middle-school Korean teacher Han Mi-jeong never learned to code. Yet the evening after a test, her tablet shows "today's answers to grade" alongside a checklist of her own criteria. A screen that reads the answers, judges them by one consistent yardstick, records the scores, and even explains them to students — she built it herself. Without a single line of code.

Eight greenhouses, six crops, 30 years of farming. Jeong Bok-san (58), who grows tomatoes in Hwacheon, Gangwon Province, was someone who used the computer only to look up market prices. Now, every morning, "Crops to check today" appears on his phone. Thirty handwritten notebooks that had been asleep in a shed — became one screen he could ask questions of. Without a single line of code, built by himself.

Nothing grand. A small tool, made one Saturday afternoon, just for myself. And that's exactly the point.