Right, but development this is correct; if you're remote and require sync, you're not actually getting things done. Meetings are not the desired outcome; deployed, working code is. Communication is necessary, but not the output, and so to be effective you have to find ways to make that communication asynchronous wherever possible. It's fine to still have the -output- be synchronous (i.e., pairing), but don't confuse the default synchronous tasks (meetings) without output.
Anyway, all of that is a red herring; don't just tell me you're remote, tell me if you're prioritizing asynchronous work or not. The places trying to recreate the office, just now remote, are not places I want to work at.
Anyway, all of that is a red herring; don't just tell me you're remote, tell me if you're prioritizing asynchronous work or not. The places trying to recreate the office, just now remote, are not places I want to work at.