A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
"Remote-first" is the phrase every company seems to want on its careers page this year. It sounds modern and generous, and it's quietly become the thing engineers ask about in interviews. But most companies that say "remote-first" actually mean "remote-allowed" — and the gap between those two is the whole game.
Remote-allowed vs. remote-first
Remote-allowed means the office is still the center of gravity. You can work from home, but the real conversations happen in the room. Decisions get made at lunch. The whiteboard photo goes to the people who were standing in front of it. If you're not there, you find out later — if you find out at all.
Remote-first means the company runs as if everyone is remote, even when some people aren't. The decision goes in a doc, not a hallway. The meeting has an agenda and notes so the person who couldn't make it isn't behind. Nobody has to be in a particular building to be a full participant.
One of those is a perk you grant. The other is a discipline you practice. Only one of them actually works.
Why this matters when you work with outside developers
We've written before that the fear of working with a developer you can't see is mostly a myth. Here's the catch: it's only a myth if you're remote-first. If you're merely remote-allowed, an outside developer starts every day as a second-class citizen — last to hear, first to be forgotten, looped in after the real call already happened. No amount of talent survives that for long.
Run remote-first and the same developer is a teammate by default. The discipline that makes your distributed team work is the exact same discipline that makes an outside developer work. They're not two problems. They're one.
The actual disciplines
Remote-first isn't a vibe. It's a short list of habits you either keep or you don't:
- Write decisions down. If it only exists in someone's memory of a meeting, half your team doesn't have it.
- Default to async. Not everything needs a meeting. Most things need a clear message and a place to reply.
- Every meeting gets an agenda and notes. A meeting with no notes didn't happen for anyone who wasn't in it.
- Judge output, not hours. "Online at 9" tells you nothing. "Shipped the thing" tells you everything.
- Over-communicate status. When people can't see you working, silence reads as stalled.
The takeaway
None of this requires a fancier tool. The tools are already cheap and everywhere. What it requires is the decision to treat writing-it-down and looping-everyone-in as the default, not the favor.
Do that and "remote-first" stops being a recruiting word and starts being true — and the difference between outsourcing that frustrates everyone and a working relationship that feels like hiring done right turns out to be this, mostly. The perk is easy to claim. The discipline is what pays off.