A “remote” team can often be in the office, when we judge valid reasons to do so. That’s what my team does. We’re not so distanced that this is a problem. Indeed, some of us visit every week. It can also mean I work with you at a coffeeshop.
Regarding naps… we take naps whenever useful. But most of us would never nap in an office. (I have, but always endured snarky comments and complaints behind my back. I once tested it: at a new workplace, I asked if they supported lying down. An ex-coworker told me of snarky jokes after I left…) Fortunately, with “hammock time” the Clojure community culturally supports horizontal-with-eyes-closed. Also, the energy boost of naps is probably healthier than energy drinks and relaxing on social media.
I know a large company that uses Clojure. Even their managers tell me “We know working remote is the future” but culturally can’t accomodate it. Ironically, I assist them in Clojure job searches, but personally would find working there painful.
I hope remote is the future. In the sphere of consumption, tech companies destroy in-person-only and replace them with remote-first-with-in-person-too (Apple Store, Amazon Go). Last week, an old retailer’s security stopped me because they spied me spending “too long” researching keyboards. They suddenly turned nice when they realized I buy more tech than average. It’s like the snarky comments again, when I’m just trying to act thoughtfully.
One counter-argument is remote is bad for developing junior programmers. But I’m happy to mentor nice people in person. And let’s look at the other side: if I were a stumbling junior (in the office) or poor (in the store), I’d be punished for deviating slightly and reasonably from the norm. Now that I’m a privileged experienced dev, I get politeness to my face and negativity behind my back.
In the sphere of production, we’re lagging, but getting there.