> Most of all I've been warning people that once you've proved the job can be done remotely, it can be done very remotely.
I disagree with that perspective. I've been remote since 2014. "Life happened" and I had to move.
When I moved in 2014, I kept my job but became remote. It worked out great for the company, too. We hired overseas. The office was West Coast and I was East Coast. I had overlap with the overseas timezones, the office didn't. I bridged a lot of communication gaps and cultural issues.
(It also helped that I had a lot of domain knowledge that was hard to replace.)
Ultimately the product finished its market window. It's becoming obsolete. I could blame "outsourcing" for why I lost my job, but that's a cop-out. I saw what our competitors were doing, and where they were beating us. I don't think the owners wanted to "keep fighting." I'm glad I got out when I did.
--
In my new role, we meet on camera everyday and have live communication. Our sales are in the US. It wouldn't work if we were outside the US.
We need to set a wide net for talent, but we also need some on-site work because we have physical things that we need to be in a place in order to manipulate. Tech isn't just in cyberspace.
So we have a mix of on-site and remote.
It's great for me, because "life happened" and I'm married, have a family, and can't move whenever my employer changes. It's great for my employer because they can cast a wide net. And because we need to "have things" and "touch stuff," our jobs aren't about to be outsourced overnight.
I also suspect that "life will happen" with everyone I work with, and our flexibility allows everyone to keep working together.
> Most of all I've been warning people that once you've proved the job can be done remotely, it can be done very remotely.
A lot of tech involves automating yourself out of a job. It's just frustrating when people don't understand that. It's hard to collect rent in technology development because someone will make you obsolete or undercut you.