|
|
|
|
|
by stingraycharles
3046 days ago
|
|
"Hiring remote engineers by flying them in turned out to be a disaster. Great engineers — and great people — can sometimes turn out to be shitty at being remote,” Smith said. “The reason is they’ve never worked remotely before and they’re not used to distractions at home so they’re on their best behavior." That's an interesting argument. I guess it's just an example and I shouldn't read too much into it, but to me the opposite is true: at home I am completely in sync with my surroundings, have no distractions and have certain "rituals" that make me more productive. It's the constant interruptions and distractions at the office that would make me terribly unproductive if someone would fly me in to assess my abilities on-site. |
|
Meanwhile, working remote, I can lay on the couch or in bed and hack meaningfully for 12 hours and do it again the day after. Actually, this is what I do for side projects while I'm on vacation, and it's how I truly de-stress and relax. It strikes me as completely strange that I have to explain this to pretty much every single (non-recruiter) person that emails me about a job about why I am only interested in remote positions. How can the tech industry be so old and this idea still so foreign?