3 ms·
I've been working remotely from about 90mi outside of Austin (for folks in Austin, doing front-end work on top of PHP). By being generally fast with email and
by scarecrowbob 14y ago
I've been working remotely from about 90mi outside of Austin (for folks in Austin, doing front-end work on top of PHP).
By being generally fast with email and generally quick/responsive I've gotten a lot of freelance work, so maybe it's just a general skills issue; it's not easy communicating certain things in email/phone/text/message and developing that as a skill takes a lot of work... it's totally subjective, but it feels that it's taken as much effort to learn when to reply to an email and when to sit on it for a half hour as it took when I first learned how to use jQuery.
IMO, this skill is made tougher to practice when the people I deal with are not also skilled at communicating; there is a lot of communication that I get remotely that takes a bit more decoding because whoever wrote it doesn't put a lot of thought into the communication.
I dunno what the good answer is; just saying "hire more experienced remote workers" sounds like a dumb answer...
- onemorepassword 14y agoNo, that sounds a lot like exactly the right answer. To promote remote working we need developers that can help and teach a company to handle remote work. Not people who will just whine about how companies suck because they don't offer remote work. Remote working is a skill, on both sides. Most companies that would theoretically not be averse to remote workers don't have that skill and can't properly evaluate that skill in others, so the only alternative to a long period of trial and error is to hire developers with a proven track record. Either that or wait for 37signal's book to come out...