Live data from Hacker News

A Short Rant About Working Remotely

ericfarkas.com

271–280 of 339 posts

Re: A Short Rant About Working Remotely

#271
post #83

Earlier quoted context omitted.

> If I need to ask a teammate a question, I turn my head slightly to the left and ask them. They respond immediately. And then they stand the chance of losing anywhere from 20 minutes to an hour of productivity thanks to your interruption. Part of the reason remote work appeals to so many of us is because we don't deal well with the constant stream of interruptions that occur in many office environments. I don't beli…

If you can't deal with interruptions, maybe teamwork is not for you. I agree that it's distracting and irritating at times, but that's the nature of working with other people.

I can usually deal with interruptions in a gracious and friendly manner. I'm a nice guy, usually laid back, and capable of rapid context switching.

I have discovered, however, that since I do not work for an emergency room, my context-switching-skills are rather undervalued by the free market. The value I generate for clients and employers is very much correlated to my ability to train clients & colleagues to let me focus on solving one problem completely before moving on to the next problem.

I find when you describe the effect of interruptions in terms employers understand — "working this way costs you money, both directly, because I charge a not-insignificant amount per hour, and indirectly, because there are opportunity costs to my working on emergencies instead of farther-reaching goals" — they will become your allies in fighting off interruptions. If you just complain that interruptions are distracting and irritating, well, you're just gonna get a prima-donna label for yourself.

I love working as a team. My creatives can make something look more visually appealing in a few hours that I could in a few months. I can develop the functionality in a few days when they wouldn't know where to start. We all have our strengths. But creative work is inherently a selfish, individual act requiring concentration, and interruptions, in most instances, don't help the team meet their goals.

Re: A Short Rant About Working Remotely

#272

Earlier quoted context omitted.

> Why aren't you answering your phone? Why haven't you responded to that email I sent you 5 minutes ago? Are you even at your computer right now? Hello??? You're confusing people who are bad at communication with working remotely being bad . Maybe you've never worked in an office environment with someone who has the same issues, but they're by no means alleviated merely by having their ass in a particular chair. > Or…

>> I'd welcome a remote employee under one condition: They're required to be on a constant video call so their on-site team members can see and talk to them at any time. > Completely laughable. Do you have closed circuit TV recordings of everywhere in the office? I'm actually working with a distributed team that does this. Everyone is on a shared video conference eight hours a day. If you want to talk to someone you…

What technology are you using for the shared video conference? I'm looking for something like this. It needs to restore connections when they die (something like Skype will reliably crap out after an hour or so, and doesn't re-establish the connection).

Re: A Short Rant About Working Remotely

#273

(lightly edited copy of my usual plea for evidence on this topic ;-) Pretty much all the evidence (rather than anecdote) I can find shows that co-located teams in a single team room environment are the most productive - all other things being equal. (And I'm saying this as somebody who spends a lot of their time working from home, and talking to other folk over Skype, etc. There are reasons for telecommuting - person…

Is it churlish to suggest that the most clear counter-example to "all in same room" is http://git.kernel.org/ However with a cursory glance over the references, they seem heavily biased towards a "crunch time, in a war-room" scenario. This can lead to large productivity gains for reasons unconnected with physical location (Clear short term goals, only the best get invited into the war-room, daily distractions and res…

Very few pieces of the kernel were actually developed by teams. One guy writes this subsystem, another writes a driver. The interactions between components are well established. Approximately 0% of the linux kernel consists of interdependent components simultaneously developed by different people.

Re: A Short Rant About Working Remotely

#274

Earlier quoted context omitted.

>> I'd welcome a remote employee under one condition: They're required to be on a constant video call so their on-site team members can see and talk to them at any time. > Completely laughable. Do you have closed circuit TV recordings of everywhere in the office? I'm actually working with a distributed team that does this. Everyone is on a shared video conference eight hours a day. If you want to talk to someone you…

What technology are you using for the shared video conference? I'm looking for something like this. It needs to restore connections when they die (something like Skype will reliably crap out after an hour or so, and doesn't re-establish the connection).

Cisco Movi/Jabber. But it was down once and we used Google Hangouts pretty effectively. If a connection dies, you just fire it back up again.

Re: A Short Rant About Working Remotely

#275
post #222

"...But I don't see a reason why, in 2013, given the tools we have, a developer has to be on-site at a desk every day, as the normal operating procedure..." I am struggling with this same question, but from the other side. I help teams become more Agile, and I'm a startup junkie, so all I care about is performance here. I want to know what works best in terms of product quality and pivot ability. And guess what? So f…

I'd contend that the tools just aren't there. When I want to chat with someone, I want to do it instantly, like walking up to someone in the office. The Skype concept of "dialing" someone is old, antiquated and feels... laggy. There was a video chat client promoted on Hacker News a while back that allowed for instantly initiating a video chat session with a colleague. Sococo, a distributed agile client (with video su…

Just leave the video conference software on. I'm working on an agile project with a distributed team and it works well once people realize that working in front of a live camera isn't any big deal.

Re: A Short Rant About Working Remotely

#276

I've been working remotely for 1 year and 3 months. The company I'm working for checks in once a week for about 20 minutes, other than that all communication is done through basecamp. I have to admit it's really hard for me and I just handed in my two weeks notice. I feel so isolated working from home and not being around other co-workers. I miss seing and interacting with other people. I'll be looking for a new job…

I've been talking to possible employers recently and I have a whole list of reasons not withstanding some family circumstances. Note that I'm talking about partial remote work, not full telecommute.

1. My commute is a drain, doing it five days a week drives me to be less motivated and productive 2. Working remotely has less distractions. 3. I know I work better when I'm not in the same place all the time, I have to mix it up or I end up staring at the wall. 4. A company that can't handle remote work has some major process issues, this is a red flag for me. 5. I have a kid, if I'm at the library or the coffee shop near home, I can come home to him at lunch. If you want to make me hate my job, ask me to spend all my time working in an office without seeing him. 6. If I can work remotely, I'm going to do more work. I'm going to keep working past 5 because I'm on a roll. If not, soon as five comes around, I'm gone.

An office is good, and having the option to come in is great. Forcing me to come in all five days a week says something bad about your culture and process. At least to me.

Re: A Short Rant About Working Remotely

#277
post #191

Earlier quoted context omitted.

How does one acquire the connections to be called in as this type of engineer?

I'm constantly learning, and seeing when things become "possible" with the current state of knowledge. Whenever I see that, on my own, I'll sketch out how the solution would work. Then, I look around for companies that need a problem I already have a solution for solved, and I pitch my solution to them. Sometimes, I'll take jobs to solve problems I haven't considered before, but that's rarer. If they like my solution…

So, in the best interview tradition, what do you read to keep up to date with the state of the art?

I have a couple of times found myself inventing solutions to problems I had in the business, only to see them appear as cutting edge open source at the same or a little later (ie Python deployment tools)

I have always assumed one needs to be working in an area, pushing hard and then finding that "what no-one has an answer to this!?" moment.

I would have trouble believing I could find a solution at the cutting edge, and find the people who needed it, without being knee-deep myself.

Re: A Short Rant About Working Remotely

#278
We ask telecommuters to work out of the office for the first two tweeks. Trying to explain the code base and the many utilities we've built is too time consuming and not easily explained over the phone or remote desktop. It's much easier to look over someone's shoulder and have discussions as needed. Moreover, we get a chance to see their personality, enthusiasm and such.

Re: A Short Rant About Working Remotely

#279

Earlier quoted context omitted.

2006 happened 7 years ago. Time flies.

Software changes in 7 years - people don't. [I mean the average person; individuals age and get more experienced, but new ones come in.] Today's homo sapiens brains function the same way as in 2006. Productivity of mental workers responds to disruptions in the same way as in 2006. A large majority of programmers and other people working now in IT are the very same people that were analyzed in 2006.

Yes, but haven't the tools for working remotely improved a lot since 2006?

Re: A Short Rant About Working Remotely

#280

Earlier quoted context omitted.

co-located teams in team-room like settings are much more productive Whenever I've seen this done, the very best employees leave. I am a firm believer that you can train yourself to hop in and out of a reasonable facsimile to the "zone" in much less than 20-30 minutes (I do it all the time)[1]; but the level of distraction of the warroom type environment massively favors your more extroverted engineers. My experience…

It depends entirely on the kind of work being done. If you've got a super-top engineer who can solve the hard problems, then they're probably working on something of their own, and can be off in their own room / at home / whatever. But in my experience, that kind of "hard", mentally intense, non-collaborative work makes up only a tiny, tiny fraction of commercial software development (although it contributes a great…

[deleted]
Post reply on HN