+1 for the information asymmetry. I'm currently working remotely 4 days a week and there are 2 other devs working remotely between 80% and 100% of the time. On

+1 for the information asymmetry. I'm currently working remotely 4 days a week and there are 2 other devs working remotely between 80% and 100% of the time. One of the main issues is "oral tradition". Information is shared from dev to dev during coffee breaks, and everyone is supposed to somehow know it. The solution is to work as if everyone is working remotely, and in that case that means putting information into writing, either by communicating through archived and searchable channels (ie Slack) or writing docs.