zlacker

I’d maybe ask what “a lot” means, because I haven’t worked with too many people who enjoy it. But regardless, when I say a job should be fully remote, I just mean it should be able/permitted to be done 100% remotely. If someone wants to do that job from the office, that’s OK too.

>>angora+(OP)
You should according to... well, yourself. But for teams who are co-located and meet up in the office 1-2 days a week, your never being around physically might be a distraction. We're not all the same.

>>estoma+M6
In your scenario, what is it about me not being physically present in person, that would constitute a distraction? Please cite sources/data for any claims you make.

edit: Also, if the answer is that the company is just not prepared with the infrastructure & culture needed to support fully-remote developers, they are closing themselves off to approximately 40% of the available talent pool, not to mention a disproportionate number of minorities and women[0]. This should constitute an emergency that must be corrected immediately in the mind of any competent CTO or engineering leader.

[0] https://www.techtarget.com/searchhrsoftware/news/365531979/N...

>>angora+7s
Yeah pal I'm not gonna cite a source to tell you about my own experiences, lol.

You fucking HN-parody.

>>estoma+p52
I apologize if asking for data hurts your feelings, and you’re obviously welcome to share your experiences as well (I did in a parent comment above).

The reason I asked for sources is that there seem to be a lot of experiences/anecdotes on both sides of this issue, but so far I haven’t been able to find too much research that supports the idea that working in person is beneficial to overall productivity, or to the company culture, or to any other company-wide metric that would justify having a mandate that all employees must work in person. If that data exists I’d like to see it, so that I can decide whether it’s worth changing my own position on this issue.