The election ended in June. Then the systems it built kept growing, the numbers it planted came home, and a new client walked in through a door the campaign had opened. A conversation about what keeps coming back after the count.
PROLOGUE · Sand and Stone
A three-page sales funnel and a stack of election projects — what does the size of a project change for you?
A grain of sand and a boulder sink all the same. So whether the thing to be built is a three-page sales funnel, a single iOS app, or the bundle of election web projects launched for the ninth nationwide local elections — the volume of a project has never mattered much to me. What matters is one thing only: whether it sinks exactly where it was aimed.
Weight does not buy speed. That is the old Pisa story, told straight. What weight changes is not how fast a thing falls but how large a mark it leaves when it misses. So I do not sort projects by weight. I sort them by the accuracy of the landing.
№ 01 · Twenty-Six Days of Silence
The morning after the count — what was left in your repository?
A victory overlay. I had prepared it the night before the count and switched it on the morning of June fourth. Three days later a commit removed the campaign office address — and then, for twenty-six days, nothing. A repository born for an election looked like it had gone to sleep with one.
Three volumes ago this magazine closed its election issue on a single word — won. What nobody tells you is what that word does next. On the first of July the winner took office. And from a meeting came not a purchase order, not a requirements document, but three sentences: the homepage has to grow beyond what it is; there has to be a system where the residents' complaints can be seen in one place; and further on, the site has to transform into a means of presenting the councilor's public work, cleanly, to the outside. Three sentences. They woke the repository up.
№ 02 · Three Sentences, Three Channels
How do three sentences become a three-channel system?
It took eight days. One day to working code, eight to every channel running live. When the dust settled it looked like this: a collector script running every five minutes inside the councilor's own Gmail; an Android app that catches SMS, RCS, and MMS off the notification rail and ships them to the server; and an authenticated admin back office where all of it lands.
What I did not build mattered more than what I did. A public complaint form — I had already built the intake API, and I deleted it. Instead of asking residents to learn a new behavior, the system absorbs the channels they already use; and a legal hole — collecting personal data with no consent screen — closed itself along the way.
There was a price. RCS does not surface through the standard SMS APIs, so I turned the design toward a notification listener — and that permission signature is exactly a smishing app's. The finished app was blocked on the councilor's own Galaxy as "suspected malicious." It was not a bug. It was the security model working as designed. The conclusion was a practical shrinking: this app will only ever live on one phone. Then no store, no signing key. One adb install is enough.
The database I chose by arguing with a trauma. During the campaign I had watched a service in this same camp die against the walls of a free tier. Instead of deciding by that memory, I put its nine causes of death in a table and checked them one by one — our workload never gets near those walls. The trauma was real, but it was workload-specific.
№ 03 · The Numbers Came Home
The numbers you could not see during election week — when did they come back?
Only after the election was over. The new domain reached the first page on Google and on Naver; Naver attached its sitelinks; search became the largest identified acquisition channel — 88 percent of identified inbound during election week. And in a July field measurement, all four AI engines answered the councilor's current standing accurately, three of them citing the official site directly as a source.
The planting happened before the vote. The harvest happened after. The count — the returns, in the old electoral sense — takes one night. These returns are still coming in.
№ 04 · A Calculator, and What Was Under It
The new client asked for exactly what — and what did you add on top?
What the client — a long-term-rental sales manager at Lotte Rent-a-Car — wanted was one webpage. A page with a quote-calculator UI that works out the price of a car. That was the whole requirement.
I added breath to it. A button that swells and settles as if breathing; a glint that sweeps across it; price digits that scramble, land, and take a highlighter stroke. It is the work of giving a dry act — quotation — a physical texture. None of it is in the requirements; leave it out because it is not, and the page becomes indistinguishable from the competitor's.
And there was a fact that never surfaced in the requirements: the competitor already had a page live. So I went one step past "build me a webpage" and said this. "Building it and putting it up is not the end. This is the age when people ask Gemini and Claude what to drink tomorrow and which car fits a newlywed couple. SEO, GEO, AEO have to be considered. I planted all three into the candidate site I built during the election, and before I met you I verified — on Google, on the Gemini app, on the Claude app, on Naver — that they surface the councilor's current standing, his pledges, and his official page accurately. I recommend we proceed."
One volume earlier, that would have been a sales pitch. It is not one now. It is a recommendation made by someone who planted the numbers and then personally harvested them. The client approved. That was the first return the election sent to this project.
№ 05 · Ten Lines, Two Sites
A new commission arrived. This time, what passed between you instead of a spec?
During the election I was handed a brief of fewer than ten lines, and I went digging — through the Tandem agency's materials and the archived campaign pages — to see how a New York candidate named Ocasio-Cortez had dealt voters a visual shock. Ten lines received; the rest I went out and found.
This time it ran the other way. Instead of waiting for a spec, I put two references on the table myself — ferrari.com and tesla.com. To give the ending away: one motif seen on tesla.com was quoted into this project. During the election I distilled principles out of someone else's campaign archive; this time the distilled eye moved first. The habit is the same — carry the principle, not the surface. What changed is that the habit now arrives before the spec does.
№ 06 · Every Panel Is a Frame
A question landed without warning — can the paper leaflet live on a screen? What did you decide, and how fast?
Out of nowhere: could the company's paper leaflet be visualized for the digital space? It was a situation that demanded a fast decision, so I handled it simply — and I know there is plenty of room left to revise. But the bones of the decision were clear.
First, I considered an Apple Cover Flow-style carousel. Second, the leaflet carries two limits — it is paper, and it is portrait — and I broke them differently per screen. On mobile, a carousel, one panel at a time. On desktop, every panel unfolds left and right at once, and only the panel standing in the center stays sharp.
A photographer said it once, or maybe a painter — that a dot, a line, brightness, that anything in this world can become a frame that summons attention. I took the remark literally. The blurred neighbors are not discarded; they work as the frame that makes the sharp center panel impossible to miss. On paper, the fold dictates your reading order. On a screen, every unfolded panel becomes the next one's frame.
№ 07 · "I Will Come to You"
The client had gone quiet. What can a developer do, standing in front of a drifting project?
This client was harder to reach than I expected. When the feedback stops, the developer is comfortable — and the project dies. So I said this: "If the project keeps drifting with no feedback, my body rests easy and the project collapses. When are you free? I will come to you. I have already built the infrastructure to develop and deploy with nothing but a tablet and my word. Today I will take all of your feedback and finish this project."
It was not bravado. Months earlier I had assembled the remote rig — a setup where a tablet issues the orders and development and deployment simply run. That is what made the sentence sayable. That day, sitting across from the client, I folded in feedback as fast as it came; the project closed its first phase; the balance was paid; search and AI-search were set. What you build ahead of need comes back like this.
EPILOGUE · What Keeps Coming Back
In English, the counted votes are called the returns. What else came back?
In English the counted ballots are called the returns — the votes come back. But in this developer's ledger, votes were not the only thing that returned. In the space the election left behind, a system grew an annex; the numbers planted before the vote came home after it; a new client walked in through the door the campaign had opened; and an infrastructure built months in advance finally earned its keep in a single afternoon.
Volume Three of this magazine closed on the word won. This volume, strictly speaking, does not close — that is its point. Of the three sentences that woke the repository, the third — the site as a clean public window on the councilor's work — is still open on the desk. An election ends in a night. The returns do not. They are still coming in, and the honest measure of the work is the one the developer named at the start: not the weight of what fell, but where it landed.
Read this interview at sass.studio.