News for hackers. Stuff that matters.
Re:Working remotely is hard by buf on Sunday November 15, 2015 @07:16PM (#10571864)
I'm the CTO of 17hats. The entire engineering team works remotely. It's not as challenging as you seem to suggest. Right now is the best time ever to be remote.

Excellent tools like Slack and Speak really help comms. We pair program very often by sshing into a tmux session which makes any lag close to nil. We use Trello for sprints. And Invision for product work. It's extremely efficient.

We have our usual retrospectives and watercooler talk and it feels natural.

Every 6 months we get together for fun.

------

The advantages of being remote far outweigh the disadvantages. Rather than listing all the advantages. What are the disadvantages?

..I'm thinking.

Re:Working remotely is hard by ygjb on Sunday November 15, 2015 @07:25PM (#10571895)
Here are some: communication, loneliness, isolation, timezones, discipline

It's really great that working remotely (anecdotally) works well for your team. It also doesn't work well for some folks. Like any other approach to business, YMMV, but discounting the disadvantages that have been enumerated for you is explicitly ignoring the fact that some people, including those who are top performing employees in their fields, prefer not to work remotely.

It's best to make the decision and your own recommendations acknowledging there are trade offs, no?

Re:Working remotely is hard by chrisan on Sunday November 15, 2015 @08:13PM (#10572070)
> Here are some: communication, loneliness, isolation, timezones, discipline

Some these can be both! I have been working remote since 2008 and our entire team went remote in 2013

Communication: We are much more streamlined. No more "hallway talk" that doesnt get recorded or followed up on etc. No more "did you get my email?" kinda crap. Much less (I won't say no more!) impromptu meetings gathering way more people than needed in the office that could have been resolved in a simple email

Isolation: I'm going to assume this is different than "loneliness"? I like isolation to work on hard problems, or just be super productive. We still video conf, phone, and chat, but outside of that all the coders love their isolation time

Timezones: This is definitely a challenge at times, but the boss man loves knowing someone is awake somewhere in the world should servers catch on fire.

Discipline: Is the person who doesn't do work at home the same one that would be checking their fantasy sports or hn/reddit/facebook at work? I guess if you were in an open office and everyone could see what you are doing 100% of the time you'd be "forced to work" but do you want that on your team anyways? You know that BS line in most job postings about "self motivated" it could actually apply for remote :)

loneliness: I can definitely see this for some people I've worked with in the past, there is no advantage to being lonely. I would say use your added free time of no commute to go out in the world and do something fun. Sometimes its great to not be around work people and not talk about work

Re:Working remotely is hard by buf on Sunday November 15, 2015 @07:34PM (#10571927)
You have a point. If someone does not enjoy remote work, then they should not get a remote job.

I'm not a very good country music singer. When I sing country music, I feel shame, discomfort, and general depression. Therefore, I don't sing country music.

Re:Working remotely is hard by gkop on Sunday November 15, 2015 @08:04PM (#10572039)
Ok, so your company only hires country singers? You are missing out on amazing, qualified candidates that don't sing country music.

Even if you are having a successful time hiring great people that are happy remote, how are you going to retain them? A remote software job is much closer to a commodity than a traditional software job. (I read the 37signals book and built a remote team over 5 years; in the end the difficulty finding people that are truly happy remote meant retention was difficult and, overall recruiting and cost of living considered, a remote team was, for me, a net wash).

Edit: after thinking more, it's even worse; you don't know if most applicants can really be happy singing country music for a year, 2 years, or longer... Even those that seem to really value and are excited about the prospect of singing country music may learn before too long that it's not for them.

Re:Working remotely is hard by Swizec on Sunday November 15, 2015 @08:12PM (#10572068)
> A remote software job is much closer to a commodity than a traditional software job

In the current climate all software [engineering] jobs are commodities from an employee viewpoint.

Re:Working remotely is hard by gkop on Sunday November 15, 2015 @08:21PM (#10572097)
True. But until we start to see the proportion of remote jobs to all jobs decline, remote is just as easily available as traditional, but lacking the physical and social stickiness that distinguishes traditional jobs and facilitates retention; remote is "closer to a commodity".
Re:Working remotely is hard by Swizec on Sunday November 15, 2015 @09:03PM (#10572219)
I guess that's true. But my inner cynic thinks that (ab)using people's herd instincts like that to "facilitate retention" cheapens traditional jobs. I would rather work remotely and have a meaningful social life, than work in an office and have a social life that my employer engineers to make me less likely to leave for a better job.

As an introvert, there is only so much social interaction I can take in a day. The office burns through most of it.

Re:Working remotely is hard by gkop on Sunday November 15, 2015 @09:08PM (#10572230)
I agree with you. I need to be more nuanced and less cold in my language. The reality is, I prefer going to an office and seeing my coworkers; fortunately this is well-aligned with the retention interests of my company.
Re:Working remotely is hard by Swizec on Sunday November 15, 2015 @09:11PM (#10572242)
As I said, I'm probably just too cynical, and seeing things through the fact that I don't like going to an office.

I agree that when it comes to team productivity rather than personal productivity, offices do work better. Especially when people of varying skill levels are involved.

Re:Working remotely is hard by workitout on Sunday November 15, 2015 @09:24PM (#10572279)
I was with you even though I've not used most of the tools you mentioned which must have been first released in the past 6 months for the hipsters. Why describe country music using terms like "discomfort", "shame" and "depression"? I can't think of any music that should make anyone feel that way. It almost seems to suggest a narrative, if you don't know what the new group of hot new tools are that were released yesterday, "Speech", "Slacker" (is that Slacker radio or Slack Linux?) and you like country music; don't bother to work for us. I'm guessing it also means if you're older than 25 no need to apply.
Re:Working remotely is hard by buf on Sunday November 15, 2015 @09:37PM (#10572307)
Not sure what you're suggesting.

We're all over 30.

Re:Working remotely is hard by percept on Sunday November 15, 2015 @07:49PM (#10571990)
As a remote worker you can sing it loud and proud.
Re:Working remotely is hard by buf on Sunday November 15, 2015 @07:54PM (#10571999)
I didn't want to rub it in.
Re:Working remotely is hard by immoderate on Sunday November 15, 2015 @08:31PM (#10572127)
I agree with you in general, I like my working remote, but it's the other guys working remote that I don't like. ;-)

Managing a distributed workforce, definitely has challenges. From what I have seen, onboarding new employees can be particularly awkward. It may be different in hip, new startups, but in my experience with less fashionable, old school organizations, it makes accountability, knowledge-sharing and organizational-political navigation more challenging.

Re:Working remotely is hard by codingdave on Sunday November 15, 2015 @07:34PM (#10571930)
Of course there are trade offs, and it works for some people, but not others. This is why if you intend to build a remote team, you hire people who can thrive in a distributed organization. You also provide the tools to make it work.

I've been working for a 100% remote company for 3 years now. It was an adjustment. But everyone who was here before me gave me advice to do well in this environment. And everyone who was hired after me got the same support and guidance. We also all get together on occasion, and when we do, we brainstorm how to do things better.

Re:Working remotely is hard by d_t_w on Sunday November 15, 2015 @07:48PM (#10571982)
I've been working remotely for the same client since late 2012, in general it's been ideal in a number of ways and the positives out-weigh the negatives.

I do miss the casual social side of having colleagues in an office from time to time, but I tend to be quite a social person. That, and maintaining delivery over a long period of time requires focus and discipline, no small effort.

Re:Working remotely is hard by AJ007 on Sunday November 15, 2015 @07:38PM (#10571941)
One this is certain, it has gotten easier. In my case I can work remote and be entirely mobile. In the past that involved a drop of productivity at least 50%.

The disadvantages are the health problems that occur if a remote worker is sitting at home all day, physically and mentally. These can take years to begin manifesting themselves and are really bad if the remote worker can't self identify them.

Re:Working remotely is hard by blisterpeanuts on Sunday November 15, 2015 @08:43PM (#10572153)
What kind of health problems? I've been working remote for about three years now and so far, haven't noticed any problems in myself.

Certainly it's made it easier to jump on the home elliptical, lift a few weights, do a few chin-ups, or run outside for 45 mins.

Back when I was in an office downtown, it was an expensive and time consuming project to go out 4-5 times a week to a gym at lunchtime or after work, then need to shower immediately before you can be around your workmates again, etc.

I'm also so much more relaxed now that I don't have to commute. That was a real stressor.

Re:Working remotely is hard by spotman on Sunday November 15, 2015 @10:31PM (#10572462)
+1 for occasionally meeting up. My team works remote and while some of us do see each other more frequent, others are on the other side of the country.

So about two times per year, once for a tech summit we go to , and another we have our own summit, we take over a hotel and hang out. During this time we also gives talks and other things but it is half fun and half work.

I think occasional face to face time and bonding time is super helpful, but not everyone needs that every day, and I think in our case it had made these twice a year meet ups something we all really get excited about and look forward too.

Re:Working remotely is hard by hamburglar on Sunday November 15, 2015 @08:19PM (#10572091)
How long have you been doing this? I'm a pretty serious introvert and I have been working remotely for about 6 years. I started out absolutely loving it but the shine is definitely off over the past year and the drawbacks are feeling like they are balancing out the benefits. The only thing that keeps me sane is if I am fairly religious about having at least two social outings per week, and even with that, it's starting to wear on me. It's possible that it's actually cured me of being an introvert.
Re:Working remotely is hard by eplanit on Sunday November 15, 2015 @10:26PM (#10572448)
This is interesting. It seems that you at 17hats built remote work into the core business model, establishing the processes and tool sets to enable and encourage it. Your story stands out as your outcome is so much more positive. The difference in your approach vs. what what most clients/companies do is that they tolerate and accommodate remote work rather than embrace and enable it. The accommodation approach, in my own experience, leads to the comms and isolation issues.
Re:Working remotely is hard by mikekchar on Sunday November 15, 2015 @10:31PM (#10572459)
I'm in the middle of a blog post of what it's like to work 9 time zones from the rest of your colleagues. There are lots of good things, but there are also a lot of challenges.

If the entire team is distributed, a lot of those challenges are mitigated. If only a few people are distributed, then you can get problems like unequal access to information, or unequal access to people. Even though my team is used to remote workers and is very conscientious, it is not unusual to have things change direction without anyone thinking to inform me. The "everybody knows" problem is pervasive.

Access to people is even more difficult. When you are working locally, it is easy to brainstorm with someone while walking to the store to buy lunch, for instance. You have a certain amount of influence on the team because conversations are low cost. Remotely, you have to come up with the idea on your own, then send an email, wait for a response, etc, etc. It is not spontaneous, which means that by and large remote workers have much less influence than local workers. Even with hangouts, IRC and slack, it's hard to generate the same banter that you would have locally (especially when you are separated by 9 timezones).

If there is anyone local who is keen on political machinations, you pretty much have to be happy with letting them have their way. You will be outmaneuvered at every turn. This places a much higher requirement for trust on remote workers. You have to trust that people will tell you about things, and then ask for your input and then wait for your reply -- rather than just doing what they wanted to do in the first place.

As I said, if you are a fully remote team, this is less of an issue. However, there are still lots of challenges in this scenario. One of the biggest surprises that I had when I moved from local to remote on my present team was how my attitude towards my team mates changed. When I was local, I went out for drinks with people, and chatted about sports and basically hung out with them. When I was remote, most of my interaction centred around code.

In the local situation, if I was pissed off about a technical issue, or something that somebody did, then my attitude towards the person was tempered by my general good feelings about them as a person. In the remote situation, my interface with people is almost entirely technical, so when someone does something I don't like, I tend to feel badly about the person as well as the issue. This is something that I need to constantly remind myself about -- they are good people doing things I don't like. It is much easier to forget this when you are working remotely, I find.

There are many other challenges as well. It's not that these challenges are insurmountable, though. You need to build a culture where people operate in the way that works for your team. It sounds like you have done that on your team. On our team as well, I don't think there is anyone remote who would rather be local, so from that perspective it works well. There are people on our team who would much rather be local and I can understand their feeling. I suspect there may be one or two people who would rather that there weren't any remote people on the team because it interferes with how they would prefer to work. I respect that too and always try to accommodate my team mates. It's a balancing act.

Re:Working remotely is hard by swampthinker on Sunday November 15, 2015 @07:23PM (#10571886)
What's Speak?
Re:Working remotely is hard by 4684499 on Sunday November 15, 2015 @07:25PM (#10571898)
Re:Working remotely is hard by buf on Sunday November 15, 2015 @07:26PM (#10571900)
speak.io

Super low bandwidth audio/video/screensharing.

Re:Working remotely is hard by abraae on Sunday November 15, 2015 @07:30PM (#10571915)
Its funny, your elevator pitch makes me want to use them. But over at their web site, they just look like a me-too skype replacement. They don't push the low bandwidth aspect at all.
Re:Working remotely is hard by buf on Sunday November 15, 2015 @07:40PM (#10571954)
They were just purchased by Slack as well.
Re:Working remotely is hard by samhoggnz on Sunday November 15, 2015 @08:18PM (#10572089)
I think you're thinking of Screenhero - https://slack.com/screenhero
Re:Working remotely is hard by buf on Sunday November 15, 2015 @09:38PM (#10572315)
Woops! Yes, you're right. Speak was originally Sqwiggle, but then pivoted. Got my S-companies confused.
Re:Working remotely is hard by velocitypsycho on Sunday November 15, 2015 @08:15PM (#10572075)
Screenhero is an amazing tool also.