Results dazzle. Reaching them is dull.
Yet what fails is always the connection.

It Starts with a Scene

INTRO · 2026

Two in the morning, in bed. In my hands, one tablet, not a laptop. I turn on its screen and connect to a small machine quietly running across the room with its display off. I change one line of code, issue a command, and watch the deployment go out. A few minutes later, that line changes in someone’s browser on the other side of the planet. I have not stood up.

If this scene seems ordinary, you already know remote work. If it looks like magic, this piece is about what happens backstage. The stage is tidy. Backstage is not.

Before reaching that scene, I saw Korean text turn to garbage, connections refused, and programs that had worked perfectly refuse to open. Search did not immediately yield solutions. This is the record of how I broke through each obstacle.

Nobody Waits for You

THE AGE · 2026

I should start with why I built this. It was not a love of technology. I witnessed two scenes.

One involved a freelancer about to get married. Requests and revisions that seemed to spring from a client’s spinal reflex arrived at night, and the client called them urgent-response items. He put aside wedding photos and honeymoon preparations and went back to work. I watched it happen beside him.

The other was at a funeral. Knowing the person was the chief mourner, the company still sent orders: company work is company work, isn’t it? Someone dressed in black was staring at a screen among the mourners. I watched that happen too.

We already live in an age when personal circumstances are no longer met with human sympathy. AI is accelerating it: once responses became available around the clock, expectations became round the clock too. You probably know this without my explaining it at length. What, then, should we do?

Resenting the times changes nothing. My chosen answer is to prepare a state in which I can respond to those demands without folding up my entire life. Instead of opening a laptop at a funeral, handle it in fifteen minutes on a tablet from my pocket and return to my place as chief mourner. That is all this piece addresses.

Some readers will probably think I am lying: what century do you think this is? I want to say two things. First, congratulations on having lived within borders and social circles where common sense works. Second, living under the same sky on the same land does not mean living in the same age or the same century. If you do not believe me, I suggest spending a summer or winter holiday in one of those cheap, dangerous countries you see on the news. You will learn that common sense is not a bulletproof vest that saves your life.

A Laptop Was Not a Server

THE MACHINE · 2026

For a long time, I did everything on one laptop: development, builds, and pretending it was a server. I left it running so I could connect and work while away. Something went wrong every time. Closing the lid broke the session. Leaving it on kept the battery pinned at 100%, wearing it down. Heavy builds heated its fanless body and slowed it.

The reason was simple. A laptop is made for intermittent use on the move, not for staying awake and responding twenty-four hours a day. A server’s first virtue is staying awake, not performance. A laptop cannot do that one thing. It is designed to sleep.

So I brought in a Mac mini. A machine without a screen, in a corner, plugged into an outlet, simply staying on. No lid to close, no battery to degrade, and cooling to withstand long runs. On the first day, I moved an entire project onto it and checked the environment again: repository, authentication, database, smoke tests. Everything passed unchanged. The work the laptop struggled with, the Mac mini did in almost boring silence.

I will call that machine a Mac mini here, because that is what I use. It does not mean you must buy one. Use a Windows desktop or stand a MacBook in clamshell mode with its lid closed; that is your choice. The point is not the kind of machine but two things. First, let the machine work in your place while you rest. Second, do not carry outside what must never be broken. Whatever its name, that role is the resident system: never asleep, always in the same place, responding whenever you connect. Your workplace is wherever you are. The resident system is that machine.

What Can Be Broken, and What Must Not Be

THE BASE · 2026

These days I browse Instagram and Threads for market research. Apps once meant for hobbies and amusement have become windows onto the market; that alone shows how times have changed. Then I saw several scenes, and those scenes made me decide to write this.

I saw a developer on the New York subway with his laptop open only a palm’s width, trying to keep Claude and Codex running. I do not know whether he had already earned his living in software or had arrived through vibe coding. I also saw a comic by a married developer team in Korea: the husband kept his laptop open from the subway all the way home like a workaholic, just to keep Claude running. A Silicon Valley developer said he left his MacBook open, connected it to his phone’s hotspot, and let Claude run agentic loops on its own for two or three hours.

But I too leave a MacBook Air at home, work from home, or operate the machine remotely from an iPad. Those scenes therefore felt strangely off. We use the same tools. Yet I do not carry the body that houses those tools.

A small joke. When I ride my motorbike around Seoul or take a night ride into Gyeonggi Province, I never put the MacBook in my bag. A human body and a bike can be half wrecked and still revive and rebuild. But the Mac, the final infrastructure that produces source code, and the code inside it that has not yet been committed—once broken, they do not come back. What you carry outside should be something you can break. What must not break stays in the resident system.

You might say an Apple service center could revive it. I have yet to meet the expert who can revive a MacBook run over by a dump truck or hit by a novice driver’s compact car. Besides, of all the laptops I have used, the MacBook died a natural death the fastest, for no reason. After it suddenly dies at fourteen months and you receive an estimate to replace every component except the display, you stop trusting Macs. Because I do not trust it, I leave it at home and operate it only remotely. This method grew out of that distrust.

Nobody Writes About Getting There

THESIS · 2026

Remote work is ultimately a matter of reach. Commands and results travel along a line between where I am and the machine over there. If the line breaks, even the most capable person can do nothing from that spot. Skill produces results, but what brings the work down is always a broken connection.

Development is the same. Code is the glamorous part: new features, beautiful screens, clever algorithms. So blogs write about code. They boast of finished screens in screenshots. But the route to that screen—how they connected to the remote machine, how they kept it awake, what they did when the connection dropped—nobody writes about that dull process of getting there. There is nothing to show off.

The problem is that getting there is exactly where beginners collapse. AI tools can write the code for them. But “I’m trying to connect from outside and it won’t connect,” “The Korean text is garbled, so I can’t type commands,” “The program starts to open and throws an error”—here people stop, search, and give up if nothing appears. Blog success stories omit this moment. The writer already got through it, or never encountered it.

This piece takes the opposite route. It records the places where I got stuck and their causes, rather than the successful screen. Because only someone who knows how to reach the machine can keep working from anywhere for long.

What This Piece Covers

ROADMAP · 2026

This manuscript builds one remote setup from beginning to end. Start with a tablet, connect to a small machine in a corner, change code, and deploy it to the world. The five installments after this introduction cover it in order.

① The machine that never sleeps. A server’s first virtue, I said, is staying awake. But left alone, machines sleep. Display settings, power options, and tools quietly preventing sleep behind the screen: how to keep the machine reliably awake through both visible settings and the command line.

② Three threads. Linking a tablet and a distant machine takes three layers of thread. One is a private network that links the two as though they were in the same room. One is a window for typing commands from the tablet. One is a net that keeps the work alive when the connection drops. How to weave the three together.

③ How to set it up. Build the remote environment by following the settings tables, from the Mac mini’s power settings to connecting Tailscale, Termius, and tmux.

④ What bloggers do not tell you. The heart of this piece. Actual errors I encountered—garbled Korean, refused connections, programs that would not open—dissected one by one into symptoms, causes, and remedies. Things search does not turn up. I can write them because I experienced them and dug down to the causes.

⑤ The first remote deployment. Finally, connect all of this, actually change one line, and send it into the world. Only a result reaching the world proves the remote connection works.

One promise in advance. This piece does not show only the easy route. When a choice disables a safeguard for convenience, I state the tradeoff there and then. Knowing remote work and blindly trusting it are different things.