3 ms·
More than logistics, the problem is a cultural divide. 6 people talk to each other constantly, but the other 3 guys are stuck on chat. There's also the problem
by hibikir 13y ago
More than logistics, the problem is a cultural divide. 6 people talk to each other constantly, but the other 3 guys are stuck on chat.
There's also the problem of remoting requiring a different skillset. I know many developers that are very good, yet they are terrible remote developers. I know one that would spend her days tweeting or enjoying her boyfriend. Another one that will fight a problem for a week instead of asking a 5 minute question. Another will undertake major refactors without telling anyone. And all those three are amazing developers while on site: You just have to keep them on an extremely short leash while remoting, and they really don't like that.
- hga 13y agoI don't like the words you're using to describe the people in your second paragraph, it doesn't sound like a problem with skillsets as we normally think of the word, or culture necessarily, at least the "culture" of workplaces. It sounds like these people have to be on a short leash, period. It's just that the leash is implicit on site, but has to become explicit in a bad way when they're remote. Although I do empathize in other contexts (especially the long term unemployed, or those not making it into the job marketplace) the general "skillsets" of working, of "showing up on time", being diligent, properly subordinate to your superiors, etc.
- cwaniak 13y agowhat he/she said makes perfect sense: it is much more difficult to keep a remote developer on short leash than an onsite developer. Makes perfect sense to me. I'd imagine most if not all folks working remotely from home don't try as hard as when in the office with peers and the boss lurking behind their back.