2 ms·
First, there is no one magical formula of totally being ok with remote working vs not. The world isn't that binary. One main issue is that these decisions nee
by j45 14y ago
First, there is no one magical formula of totally being ok with remote working vs not.
The world isn't that binary.
One main issue is that these decisions need to be made based on the discipline of the developer to work well in their own time. It's not an issue with self-directed and self-teaching developers, but the simply, just, aren't.
I've worked remotely for a good 5-6 years now. You really have to still be reasonably available by phone, IM, and for meetings as reasonably needed. You have to provide benefits only available by distance.
One that I share a lot is remote screen sharing. You have to cram in beside each other on a computer, so pair programming actually works not bad if you need to help someone, or do something together.
Sometimes I have to give up an afternoon to do a larger "state of the project" meeting once a month, which is fine. Ultimately it's about a balance that all projects need. You do get some benefits from being in the same room with the right people that you won't distantly. With those right people, though, you could probably be away. The problem comes in when you're dealing with a productivity level that is average because of the people involved.