I work in design and planning at a UX/UI company in Korea. But most of the tools and methodologies I use come from the United States. When a new tool comes out, I read the English documentation, then translate it, and it takes a long time to adapt it to the Korean context. By then, yet another platform has already been updated. So we always learn one beat behind. Today, as always, countless updates keep arriving.

When I met Joseph in Korea, he was running a workshop at Ururu called Why printers do not work on their own.

He did not describe a printer as a machine that breaks sometimes. He described printers as machines that stay in an almost working state. They are not fully dead, but they are not reliable. When something goes wrong, it is not only that the machine broke. A situation appears where I have to step in.

His explanation did not sound like the tech critique I usually hear. He did not focus on blaming technology. He focused on how technology keeps moving us from the role of user into the role of administrator. Error messages, warnings, ink, settings, updates. These details produce the same scene again and again. A human enters the space where the machine does not take responsibility. Because it happens often, it starts to feel normal.

While he spoke, I kept thinking about the web.

I am a web developer. As I listened, I thought of pages, logins, caches, compatibility, loading, permissions, updates. If printers keep summoning the user back into the system, the web does this more often. The web looks smooth on the surface, but it calls us back repeatedly.

As a user, the web presents itself as simple. Click and it works.

The routine feels different. Click. Wait. Refresh. Log in again. Approve permissions again. Update. Search the error message. Try again.

I maintain work for clients in the United States. So when I should normally be going to sleep, that is exactly when they are most reachable. On launch days I sometimes stay awake for two or three days straight. The most difficult moments are when everything works fine on my hardware but errors keep appearing only on the client's side. I was paid, so I am responsible. But the error is not in front of me, so it looks like I am avoiding responsibility. That is how I suddenly find myself facing the anxiety of being two outs in.

I want the websites I build to feel light and kind. I call that feathery. I have learned that this idea carries many small responsibilities. Making something lighter is not only removing features. It means reducing failure across more environments. It means anticipating more failure and accepting more exceptions. It is not letting the web run on its own. It is holding up the places that are close to collapse.

Last night I lay down to sleep again. But the code kept running through my head. Where it was going wrong, which line might fix it, it just kept looping. Even when I closed my eyes, the thought would not stop. After tossing and turning for a while, I got up and opened my laptop. I changed a few lines and ran it again. Still not working. Fixed it again. Ran it again. Most of it stayed the same. I kept repeating the same thing over and over. I knew time was passing, but I could not stop. Because if I just lay there, the code would keep running in my head anyway. So I kept going a little longer, and only when I felt like I truly could not go on did I close the laptop and lie back down. Even then, sleep did not come right away. There was still a light on somewhere in my head.

Then I thought about what my day looks like.

I check the mobile view on a phone and the desktop layout on a tablet. One laptop is for documents, email, and feedback. Another laptop is for code. Some days I join a video call late at night because of time zones. Some days something is urgent and I borrow a friend's laptop to push a fix. Search stays open all day. This is not about liking devices. It is because the web is not a finished object. I keep circling it, checking, patching, reconnecting.

Why does the web not work on its own. This question does not stop at inconvenience. It leads to another question.

I cannot say exactly what I do, but my work is related to security. Here, doing the work and proving the work are almost the same thing. Every document I read, every site I referenced, every prompt I used is recorded. The company calls it data for productivity and security. So sometimes I feel less like a person doing the work, and more like a person producing evidence that work is being done.

Just a few years ago in Korea, six months of coding training practically guaranteed a job at a major company. I learned development through a government-funded program. Naturally, the tuition was free. But then AI tools arrived. Now when I go to the places the government matched me with, I get turned away before even reaching the interview. There are countless people like me. Many of them quit their previous jobs to pursue this one.

The government still cites its subsidized training programs as a top achievement. I am still unemployed.