Remote Work Feels Great. The Data Says It's Making Us Lonely. What Devs Can Do

New research out this month keeps landing on the same awkward split: people love working from home, but the numbers on isolation and mental health point the other way. It’s worth a pause if you’re a developer. A lot of us went fully remote years ago and never looked back.

What happened

In a June 18 New York Times opinion piece, “We Liked Remote Work. Then We Looked at the Data.,” economists Emma Harrington and Natalia Emmanuel argue that what workers want and what’s good for them have split apart. About 80% of workers said they’d prefer remote arrangements in 2024 (per WFHResearch), even as the evidence on the cost of all-day solitude keeps stacking up.

“Most Americans say they love working from home,” the authors write. “They can skip their commutes, dodge their snippy co-workers and evade their micromanaging bosses.”

It’s not a one-off finding. On June 8, NPR covered a separate study that reached the same conclusion: remote work stays popular, but the isolation takes a measurable toll on mental health. The pattern holds across the survey data. Fully remote workers report more loneliness than their hybrid or in-office peers, and even one or two days of in-person contact a week seems to soften it.

Why it matters

The remote-work debate usually gets framed as productivity versus office real estate. This research reframes it as a health story. The exact thing that makes remote work great for focus, long uninterrupted stretches of solitude, is the thing that quietly starves you of social contact if you let it.

Developers sit at the sharp end of this. The job already leans solitary: long stretches in an editor, async everything, headphones on by default. Add a fully remote setup and you can easily go a whole day, sometimes a whole week, where the only human contact you get is a pull request comment.

What this means for developers

The takeaway isn’t “go back to the office.” It’s that connection has to become a deliberate habit now, because remote work stopped supplying it by accident. A few that fit around a developer’s day:

• Get one live conversation on the calendar every day. A pairing session, a quick call instead of a long Slack thread, a virtual coffee. If it isn’t scheduled, focus mode will eat it.
• Leave the house before you’ve “earned” it. A morning walk or a midday gym block isn’t a reward for finishing work. It’s part of what keeps the work going. Anchor it to a fixed time so it doesn’t slide.
• Separate “alone and focused” from “alone and isolated.” Deep work needs solitude. Your evenings and weekends shouldn’t inherit it. Block out at least one in-person thing a week and guard it the way you’d guard a deploy window.
• Track it like any other habit. If “talked to a human today” and “left the house” were streaks you actually watched, you’d catch the bad weeks before they pile up.

About 80% of workers said they’d prefer remote work in 2024, even as the isolation data pointed the other way. (WFHResearch)

The bottom line

Remote work isn’t the problem. Unstructured remote work is. The developers who do well over the long run won’t be the ones who white-knuckle their way back to a commute. They’ll be the ones who build connection and movement into the week as deliberately as they keep a commit streak alive. Treat your social life like infrastructure: if you don’t schedule it, it goes down quietly and nobody pages you.