https://fortune.com/europe/2025/02/24/stripe-billionaire-collison-brothers-remote-work-solves-two-body-problem-faced-working-couples/ Reading this made me curious, so I thought I'd ask. What is the typical remote situation like for Clojure devs? are most folks remote? fully in-person? in-between?
"Working remotely has had a bunch of benefits where there's a way larger talent pool available to companies," John told the podcast. He touched on the potential knock-on effects of enabling this talent pool to work from anywhere, and how it might help address the sociological phenomenon of the "two-body problem."
"You see kind of the two-body problem, where it allows a lot of couples, where maybe one partner is assigned to some hospital in Idaho, and they don't get to choose what hospital necessarily they got assigned to, and the other person gets to work a high-paying tech job."
His brother Patrick elaborated: "I think one of the theories for declining dynamism in the U.S. and declining TFP [total factor productivity] is that allocative efficiency of people declined as women entered the workforce because now you have…this two-body problem where both people have to make coordinated switches…and remote work solves that."I suppose there's problems hiring remote people as contractors instead of as employees? (To work around the bureaucratic problems of hiring employees remotely)
Contractors and employees are in different budgets, so it's a different bureaucracy.
I don't know about "typical" but I've been almost 100% remote since 2007, a few years before I picked up Clojure. I worked at a startup in 2008/2009 that was hybrid (usually 3 days in the office) but otherwise completely remote...
Two-body problem was a bit of an icky term. 😃 But I agree that unlocking some hard constraints can really smoothen things for people and enable them to make sweeter choices.
Would be interesting to see a study of the share of remote workers across languages and technologies.
When I was laid off and looking for work, I would see job postings for in-office-required work and think to myself, “these companies are really missing out on good talent by requiring in-office.” I had worked in office up until March 2020 and laid off in July 2023 because the start up I was working for ran out of runway. And I was only applying to remote work because my husband’s job required that he stay local and we also are at a stage where being easily accessible to family needs is important. And I know so many other people in the same situation. I could go back to office full time in about 6 years, but not before then. I found that there were a lot of remote Clojure jobs. It’s the bigger companies that seem to require time in office- start ups tend to be more open to remote, though I have been getting headhunted by (non-Clojure) startups that require in-office in San Francisco.
I don't know about "typical" but I've been almost 100% remote since 2007, a few years before I picked up Clojure. I worked at a startup in 2008/2009 that was hybrid (usually 3 days in the office) but otherwise completely remote...actually come to think of it, a lot of the postings I've seen in these channels havent been truly remote. At least not in the sense of being truly worldwide remote. I've seen some "region-remote" openings... but the worldwide remote options are fewer. > Two-body problem was a bit of an icky term. 😃 🙂 yes. The term is also so generic and vague that you would really need to already know the definition to know what they're talking about. > I had worked in office up until March 2020 and laid off in July 2023 because the start up I was working for ran out of runway. And I was only applying to remote work because my husband’s job required that he stay local and we also are at a stage where being easily accessible to family needs is important. And I know so many other people in the same situation. I could go back to office full time in about 6 years, but not before then. yes! this is so me in a lot of ways.
I've been doing mostly remote work since 2013 with that initially being at a small start-up that embraced Clojure. We would not have been able to hire the talent (skillful programmers that either had any Clojure experience or were excited to learn it) we did without being a remote based company. Being able to hire folks wherever they are and retain them through life events (or choices) that require moving is huge.
@jf.slack-clojurians Yeah, there are lots of reasons for this: > worldwide remote options are fewer. While you can argue that timezones are not really a barrier -- if employees are willing to work strange hours to be available for real-time chat and meetings with coworkers elsewhere in the world -- but there are often a lot of logistical, financial, and legal reasons why a company can't just hire someone in a different country: taxes, healthcare benefits, employment law. Even within the USA, it can be difficult for smaller companies to hire outside their "home" state due to restrictions on health insurance plans or employment laws, and it is certainly made more complex by different states having different income tax, for example -- or no income tax in some states. Where I work is 100% remote but was almost entirely US-based for most of its time -- until the pandemic when a few employees decided to move from California to Europe to be closer to family. We've found ways to make that work but it is non-trivial for the business.
> Being able to hire folks wherever they are and retain them through life events (or choices) that require moving is huge. This tends to be more true for small companies than large companies, since the latter tend to view employees as more fungible -- while the irony is that the larger companies can better afford to support remote workers (in the areas I mention above). They just often choose not to, for "company culture" reasons, esp. if their management lean toward RTO mandates in the first place 😞