Field

A production line has one set of numbers and several people reading them at different densities. The shift lead reads this minute, the manager reads the day, quality reads one window. Until now that was one development project per screen. When the description sits on the device side, the arithmetic changes. Plus what actually went wrong getting values onto an instrument screen.

Greenhouses change equipment often. A sensor goes out of production, another company's part goes in, and until now the control code was edited every time. When a node declares itself and rules speak in kinds rather than model numbers, that editing disappears. A sample runs the same server twice against two entirely different installed sets — and one race condition it caught along the way.

Moving this volume's wheelhouse picture into an actual structure, written from what was measured with three nodes on one page. Each machine gives its own screen, each tile's button reaches its own machine, and one going dark leaves the rest alive. What the equipment side fills in when this moves to a ship is stated too.

Two cafés share the same counter screen. Prices, hours and menus differ, and one quotes tax-inclusive while the other adds it at the counter. Not one character of either shop's name appears inside the bundle, and the verification protects that with a single grep.

In 2026-06 we ran a piece about a tax practice's deadline board. That piece never said where the dates came from. This time we built it — and this board stores no deadline at all. It computes from rules every time, and when a date slipped past a weekend it says so.

Since the launch issue this magazine has been writing that it never tested offline behaviour. This time we killed the till process mid-run and took three more orders. Losing them and taking them twice are opposite failures, so both are checked.

What gets lost at handover is not the item somebody forgot. It is the item that appears at every handover all week and that nobody touches. Once the board stopped being retyped and started being carried, the number of times it had crossed counted itself.

In 2026-06 we ran a piece about a sole trader gathering several roles onto one screen. Gathering everything onto one screen is just a list. The hard part is trusting that list on your own — so every item comes out carrying its source, and the sort rule is written on the screen.

An order arrives in the sequence the customer typed it; the picker walks the racks in the sequence the racks are in. Instead of asserting that the two differ, we computed both routes and put them on the screen. 106 steps and 82.

Managing a queue means two people in two places looking at the same line. The moment the door and the counter each start remembering their own number, an argument with a customer follows. We built two screens, called one party from the counter, and re-photographed the door screen nobody had touched.

With four terminals in a taxi, what joins them is the driver's hands. The door opens and the meter starts, the speed frames the vehicle sends become a fare, and on arrival payment appears on the passenger screen. In one trip a human pressed one button — the passenger's "pay". Full source, run log, eight real render captures.

A shop that sells by weight eventually finds the day off by a few hundred won. Because the price is calculated twice — once rounded so a customer can pay it, printed on the label, and once from the original weight into the ledger. Both are reasonable and they differ.

In 2026-05 we ran a piece about inheriting a father's work notebook. The difficulty of an inherited record is not reading it but not knowing who knew what and when. This time we built it — here nothing is overwritten. A line proved wrong stays exactly where it is, and why it was believed stays readable.

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.