You kept the machine awake, linked it with three threads, and avoided the traps. What remains is proof. Remote access exists when a result actually reaches the world, not when a switch is set. In this final chapter, connect to a machine beyond arm’s reach, change one line of code, and deploy it to the world.
§ 00 · Change One Line and Send It Out
Now actually do it. Attach to the net from the tablet. Your working position returns unchanged. Edit one line of code. Watch the automated checks run and pass. Then push to the repository. At that moment, deployment goes out.
A few minutes later, the line changes on a screen in the world. With one tablet, without standing up, I made the machine across the room do it. I have done this entire sequence in bed before dawn, on the subway, and in a café. My workplace was wherever I was; the resident system stayed in its place.
What matters is proof, not spectacle. Not the machine’s claim that it “deployed,” but the one line actually changed on a screen in the world. The evidence of working remote access is one result that reached the world, not a settings screen.
§ 01 · What We Disable for Convenience
As promised, I will not show only the convenient route. To work smoothly remotely, you may want to turn off some safeguards: disable the confirmation that asks whether each action is allowed so work flows automatically, or keep credentials in a file rather than type a password each time.
These choices offer convenience. They also trade something away. Disable confirmations and irreversible commands run without asking. Store credentials in a file and the door opens the moment that file leaks. I chose with awareness of the tradeoff. Knowing and switching something on unknowingly are different.
So one rule: when disabling a safeguard, say aloud, right there, what it was protecting. Understanding remote access and blindly trusting it differ. The more convenient the route, the more readily others can enter by the same route if it is breached.
§ 02 · Place Must Not Bind Your Work
Once remote access is in place, your workplace is no longer a desk. You can reach the machine from bed, the subway, or a roadside convenience store where you have parked your motorbike. Leave what must not break in the resident system at home. Carry only a thin tablet that may be broken, and go anywhere.
This was the opening scene: two in the morning, in bed, changing one line in the world with a tablet, never standing up. Now it is a procedure, not magic. You have seen everything backstage.
One last thing. Learning to reach the machine is dull. There is nothing to boast about. Yet while skill creates one result, the person who keeps working is always the one who can reach the machine anywhere. May your location never bind you.
§ 03 · Doubt the Most Trustworthy Person
I always tell my non-developer acquaintances and my students one thing: never believe the blog that writes a single line and says “anyone can do it.” That caution still holds in this age when tools supposedly do everything for you.
There is evidence. The issues actually encountered while building this remote infrastructure and troubleshooting list could occasionally be found on technically oriented blogs such as Velog and Tistory. But I found not one in places such as Instagram, where quick uploads and visibility come first. The screen retains only the successful line. The blocked places are written nowhere.
Andy Warhol said his words were valid for only one week from that moment. All information is like that: there is no guarantee it will remain consistent a week later. So I close this series with one line. The person who seems most trustworthy should be questioned first.
The settings and code in this piece also need checking on actual devices. After connecting, read files, resume work, and verify that the changed code was deployed.
Read this note at sass.studio.