Remote work isn't new in tech. But the way we talk about it — like it's some revolutionary discovery — kind of is.

The reality? Developers have been SSHing into servers from coffee shops since before "digital nomad" was a LinkedIn hashtag. What changed is scale. COVID forced every company to try it at once, and it turns out a lot of the old arguments against remote work didn't hold up.

How we got here

Four years ago, offices emptied overnight. Not because companies had some grand vision for the future of work. Because they had to.

And then something interesting happened. The world didn't end. Projects shipped. Code got written. Some teams actually moved faster without the constant interruptions of open-plan offices. (Shocking, we know.)

Tech startups were especially quick to embrace it — partly out of necessity, partly because the tooling already existed. Slack, GitHub, Zoom, Notion. The infrastructure for distributed work was sitting right there. Most companies just hadn't bothered to use it properly.

What actually works about remote

People get their time back. The average commute eats 40-60 minutes a day. That's five hours a week spent in traffic or on trains, doing nothing productive. Remote work hands that time back. Some people use it for exercise, some for family, some just sleep an extra hour. All of those are good outcomes.

You can hire from anywhere. This is the one that changed things for us. When you're a startup in Zürich, the local talent pool is strong but competitive and expensive. Remote work means we can work with great developers regardless of where they happen to live. That's not a minor perk — it fundamentally changes what a small team can build.

Productivity goes up, not down. This surprised a lot of managers. Turns out people are pretty good at managing their own time when you trust them to do it. The data backs this up consistently, even years after the initial shift. People work during their most productive hours instead of warming a chair from 9 to 5.

It costs less. Less office space, fewer overheads, no commuting subsidies. For startups watching every franc, that matters. We'd rather spend money on building product than on a fancy office nobody needs five days a week.

The hard parts (because there are hard parts)

We're not going to pretend it's all great. Remote work has real problems, and glossing over them doesn't help anyone.

Communication gets weird. When you can't tap someone on the shoulder, everything becomes a message. And messages get misread. Tone disappears in text. Someone writes "fine" and you spend twenty minutes wondering if they're actually fine or passive-aggressive. Time zones make it worse — you ask a question at 4pm and the answer comes at midnight.

Spontaneous collaboration dies. Those random hallway conversations where someone overhears a problem and says "oh, I know how to fix that"? They don't happen on Slack. You can try to manufacture them with virtual coffee chats and random pairing, but it's not the same. We haven't cracked this one honestly.

Loneliness is real. Especially for people who live alone or are new to a city. Your colleagues become usernames and profile pictures. Some people thrive in that setup. Others slowly burn out from the isolation. There's no one-size-fits-all answer here.

Managing performance is harder. You can't measure output by who's sitting at their desk looking busy. (You shouldn't have been doing that anyway, but a lot of managers were.) Remote forces you to actually define what "good work" looks like and measure results instead of presence. That's better in theory but harder in practice.

Not everyone has a good setup. A developer with a dedicated home office, fast internet, and a good chair is going to have a very different experience from someone working from a kitchen table in a shared flat with spotty WiFi. The inequality isn't always visible.

Boundaries blur. When your office is your living room, it's hard to stop working. The laptop is right there. Just one more email. Just one more PR review. We've seen people burn out not because remote work is too easy, but because they never actually leave work.

What we've learned at Pyango

We're a small team. We've done fully remote, hybrid, and in-person at various points. Here's what we've landed on:

Remote works if you're intentional about it. Default to async communication, write things down, and don't schedule meetings for things that could be a message. But also — get people together in person regularly. Not every day, not even every week necessarily. But often enough that the team feels like a team and not just a group chat.

The tools matter less than the habits. We've seen teams with every collaboration tool imaginable still fail at remote work because nobody established norms around how to use them. A shared doc culture beats a fancy project management tool every time.

And honestly? The biggest thing we learned is that it's not about remote vs. office. It's about whether your company trusts its people. If you do, remote works. If you don't, no amount of office surveillance software is going to fix that.

Professional growth in a remote world

One thing that doesn't get talked about enough: junior developers have it rough in remote setups. The informal mentorship that happens when you sit next to someone experienced — watching how they debug, picking up patterns from code reviews done shoulder-to-shoulder — that's genuinely hard to replicate over video calls.

We don't have a perfect solution for this. What we've tried: dedicated pairing sessions, async code review with detailed comments, and being very explicit about things that would normally be caught through osmosis. It's more work. But it's necessary work if you want people to actually grow.

Training programs need rethinking too. A four-hour Zoom workshop is not the same as an in-person training day. Shorter sessions, more hands-on exercises, better documentation. The format has to change when the medium changes.

Where this is going

Remote work isn't going away. But the hype cycle around it is settling into something more realistic. Most companies will end up somewhere in the middle — some remote, some in-person, figuring it out as they go.

The companies that do it well will be the ones that treat it as a skill to develop, not a policy to enforce. Communication, documentation, async collaboration — these are things you get better at with practice. The ones that just threw people home with a laptop and said "figure it out" are the ones now demanding everyone come back to the office.

We're still figuring it out too. But four years in, we're pretty sure the answer isn't "go back to how things were." It's "get better at how things are."

Remote work & culture challenges in a startups

Latest blogs