Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I'm actually not in favour. It has the downside that you are not in direct contact with the people you need. In the office the contact is too direct where people walk up to you to fix their shit while your work is delayed because of that. There is no in between
@EngineerCoding What's the option in an open office? Pulling their headphone cables? In a remote environment people have to keep a watchful eye on their slack notifications if they are expected to be available for communication. Call via slack, screen share when needed. Everything you need to collaborate is there. To each their own but I don't see why there would be any critical collaboration issues by working remote with all the resources we have. If there are any, they would likely be cancelled out by the massive benifit that working remote could provide. Again, it's not for everyone. My own ideal strategy would be 2-3 days remote. But my point on collaboration remains.
Edit: I agree with you on not sharing phone numbers (at least not private numbers), Slack should be enough.