Live data from Hacker News

A Short Rant About Working Remotely

ericfarkas.com

141–150 of 339 posts

Re: A Short Rant About Working Remotely

#141
I've experienced both styles for extended periods. I've worked with some really hard core engineering teams during my many colocation years and remotely for the past 2.5 years.

Over the years of working with many great people, I had built a habit of potentially over-collaborating with my peers. It was hard not to, considering how much smarter two people are than one. And with the right mixture of personalities and solving hard problems, it's almost always more enjoyable (even delightful) to work things through together. You get the stronger sense that together you are delivering a greatness that would be hard to achieve on your own.

I've really missed that part since I've been remote for the past few years. However I have had to learn to be way more self sufficient and resourceful. I think initially the transition hurt my productivity somewhat, but it also ended up making me much stronger and decisive because I couldn't fallback to the whiteboard anymore.

I think I still prefer the colocation style to some degree because working closely with great people is just so rewarding. Thankfully even while I'm currently in my fortress of solitude, I still have great peers to work and connect with through Skype. We have a team chat going all the time that is similar to the war room arrangement where we can socialize and discuss random (sometimes even relevant) topics.

All in all, working with great people is the key either colocated or remote.

EDIT: I should also mention that your ability to focus on your own dev work is great for personal productivity, but often your full value to the team is only realized when you shift your focus to helping the team. I've had many situations where I could have used one of those ticket dispensers because the line at my desk was out of control. I found that working from home for 1 or 2 days a week was a good balance in that situation. Time for some self focus and time for giving to the team.

Re: A Short Rant About Working Remotely

#143
post #123

A few notes from someone who's worked remotely roughly 60% of the last 10 years - 1) Most investors know that startups are generally at a disadvantage with a remote team and give founders shit for hiring remote people. I've found thats one of the reasons early stage folks don't hire more remote people. And there is some truth to being more creative with a team around you... if the team is awesome. Also communication…

Have any good contacts at these "boring consulting businesses"? I am not averse to an unsexy (remote) job.

Saw that you connected on Linkedin if I hear of anything I'll let you know

Re: A Short Rant About Working Remotely

#144
post #83

Earlier quoted context omitted.

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.

Most people believe they are able to deal with interruptions. Very few people are actually able to do so in an even remotely efficient manner.

Still teams of gifted individuals tend to achieve more than sum of gifted individuals working alone, distractions notwithstanding.

Anyway I'm reserved about the very thesis that office life is particularly full of distractions. At home office you might have spouse and kids who are even less understanding of your "zone" than your coworkers. If you are single it might be neighbors driving their renovation project with hammer drills at work hours. You probably have a TV, game console, your guitar, your pet, and basically have to rely on self-discipline with that.

Re: A Short Rant About Working Remotely

#145
"...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 far it's co-located teams that kick ass over distributed teams. I wish it wasn't so, and I'd love to hang back in my home office and work, but that's not the way the numbers are looking.

To be more precise, yes, you can become a "commodity" programmer, that is, somebody that people slide a list under the door to and who delivers code on a regular basis. In this case you are competing with commodity programmers around the world who are willing to work for peanuts. If that's your thing, hop on over to one of the programming job sites and have fun with it.

Now I can already hear the objections. With all these tools, why can't I be just as plugged in as if I were in the office? Aren't you making a false dichotomy, asking us to either be on-site or completely on our own?

Yes, I am generalizing. Look, I don't know why the tools don't work to do the things they are supposed to do. Certainly we have chat, VOIP, and all kinds of awesome communication tools. You'd think that would be enough. But it's not. Instead of powerfully performing teams we get mediocrity.

I suspect that software development has a powerful social and human aspect that is not replaced by tools. Working in a team isn't just trading streams of data across a wire. It's going out to lunch, having a beer while talking about work, or making an oddball suggestion one Wednesday afternoon that turns out to change how everybody thinks of the problem they're working on.

So sign me up for remote work too. Just show me how it's going to be as effective as co-located teams. I see a lot of fluff from places like 37Signals who make a marketing strategy out of being so aweseome, but I'm not seeing results in the real world. I hope to learn more -- and I hope this problem gets solved.

Re: A Short Rant About Working Remotely

#146
post #121

I have got chance to work both in 9-5 environment as well as working in isolation. Working for home was my own choice so that I can give time to my infant kid which is most important for me. Working from home gave me relaxation. I could work on my chair or on my bed, nobody was going to ask me how I sit. Second most important thing which helped me a lot was to have a feeling of helplessness . When you work in an offi…

This is why most people don't get to work from home. Spending time with your kid and being constantly relaxed, working from bed, is counter to the serious business culture of most companies. Don't take this the wrong way, and it's not a dig, but from the way that you wrote that, it sounds like you only work a few hours a day casually.

I can see why Big Bank X would not allow their employees to do that.

Re: A Short Rant About Working Remotely

#147

(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…

A lot has changed in the last few years-- with modern tools (Skype, Google Hangouts, IRC, GotoMeeting), it is possible to not only almost entirely replicate being co-located, but to even enhance productivity by spinning out ad-hoc co-located teams to solve individual problems. Need to have a concentrated task force from 5 various departments? No problem, it's a click away-- no need to book a meeting room, take all yo…

This. There's free technology to solve most of the remote workers' problems.

Re: A Short Rant About Working Remotely

#148

(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…

Not saying that you are wrong, but none of the studies you quote was done in the last five years, and most of them are actually more than a decade old.

The technologies we use to communicate evolve fast, and I would bet money on the fact that (probably because of mindset evolution and tooling) developers are now more efficient when working remotely than they were ten years ago. Moreover, as we are on HN, we are not necessarily talking about average developers, but more about the ones that are used to Git, IRC, Trello, and other tools which make remote work more doable.

Startup environments are not average, and this must be why companies like Github and 37signals can be successful while having remote workers.

Re: A Short Rant About Working Remotely

#149

(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…

1. How do you define group productivity? 2. I'm willing to bet that most of those studies looked at what happens when you take some "on-site" positions and simply hand them to remote team members. Why? Because that's what usually happens. Companies do not want to alter any processes, team structures or responsibilities to explicitly deal with remoteness. Naturally, if you pretend that someone from another state is sitting in the next cubicle, bad things will happen. Companies that embrace remoteness from the start (like GitHub) seem to be doing fine, precisely because they treat remoteness as an asses, not a minor concession someone had to make to workers.

Re: A Short Rant About Working Remotely

#150
post #119

I'm personally not a big fan of remote workers. Not because I don't think the tools are adequate or that I trust they are actually working. I think there's something special that can't be reproduced when a small team that's just starting out is physically together. I've been at a few startups and I can't count how many times a good idea or breakthrough came while we were out getting lunch, a beer or playing pool in t…

Is it really that difficult to type your question into skype or campfire group chat? We're all remote and we have daily 20 minute video conferences, and everyone is always logged into campfire. It's the most productive team I've ever worked with, and if someone isn't pulling their weight, you can tell from their git commits. Every argument I've heard against remote working boils down to that "something special" you m…

It's not the day to day interactions. Hell, most of the companies I work with that aren't remote chat over IM and group chat while we sit next to each other. As I said, I don't think it's a breakdown of the tools. It's not that people aren't productive either. It's the "other" stuff that doesn't fit into those categories. There's no technology to replace sitting around with a group of guys having a beer. While its vague, it's just a different experience that Skype or group chat. It's a different setting and a different mindset. The things that are special are the things that don't fit into the normal daily workflow. For many companies remote teams might make sense and even strive, this is just my personal opinion of what I think is missing. So much of it depends on the company, the culture and the people.
Post reply on HN