Fully Remote vs Hybrid — Which Is Actually Better?

What I Realized on the Subway

First day of hybrid work. I took Seoul's Line 2 — Sadang to Gangnam station, 47 minutes. I'd forgotten this sensation after a year of full remote. The smell of people, sweat, someone else's music leaking through earbuds. The commute home took 53 minutes. That's 1 hour 40 minutes a day on the subway.

During full remote, I used that time to exercise. Well, honestly, I exercised for the first two months. After that, I just slept 30 more minutes.

What Was Good About Full Remote

Deep focus time was undeniably better. I could code for three uninterrupted hours in the morning. In the office, you get the shoulder tap — "hey, quick question" — maybe six times a day. Even at five minutes each, that's 30 minutes, plus 15 minutes each to regain flow state. Two hours gone.

Lunch was flexible. Eat at 11:30 or 2:00 — nobody cares. A quick nap after lunch was possible. (This genuinely helps productivity. Science backs it up.)

Phone calls were easier too. In the office you need to book a meeting room. At home, you just answer.

Around Month Nine, Things Got Weird

Not seeing people made me develop strange habits. Wearing the same clothes three days straight. Not showering until 11 AM. Going entire days without speaking a single word out loud. I sent Slack messages, but I didn't "talk."

The worst part was the boundary between work and life dissolving. Slack notification at 8 PM — "let me just check this" — laptop open until 10 PM. Full remote became full-time work. I actually tracked it: post-work hours averaged 4.2 hours per week during full remote. (Measured with a timer app.)

After Switching to Hybrid

Three days in office, two days remote. At first, I thought it was the worst of both worlds. Commute days were exhausting, remote days felt incomplete with "but I have to go in tomorrow" hanging over them.

But after a month, I adapted. Surprisingly, clustering meetings on office days was efficient. Code review that takes 30 minutes face-to-face stretches to half a day over Slack. One quick "why'd you do it this way?" in person versus paragraphs of context in text.

On remote days, I focused purely on coding. I fixed those as no-meeting days, and got 6 hours of pure development time from 9 to 5. Absolutely impossible in the office.

The Honest Assessment After Trying Both

There's no right answer. Truly none. It depends on the person, the team, the project.

If you do a lot of deep solo work, full remote fits. If your team collaborates heavily and needs fast decisions, hybrid fits. But that's the textbook answer. Reality is "whatever your company tells you to do."

I ended up slightly preferring hybrid for a simple reason: seeing people is better for my mental health. That subtle isolation I felt at month nine of full remote just doesn't happen with hybrid.

But that 1 hour 40 minute commute is genuinely painful. I could've built another side project in that time. (Honestly, I wouldn't have, but the possibility mattered.)