Live data from Hacker News

Remote Working – 3 Year Retrospective

blog.jonliv.es

21–30 of 68 posts

Re: Remote Working – 3 Year Retrospective

#21

The part about "Substandard Treatment" hits home for me. When I first went remote the hardest that was the hardest thing for me to adjust too. Lunches and/or dinners being bought for them, weekend team trips, etc. It's a trivial thing in the grand scheme of things, but it can affect morale.

"weekend team trips"

Also jealousy issues... Realize that most people can't stand those things and it tends to turn into a test of personality, who will kiss up no matter how awful the experience, or who has the guts to admit the emperor has no clothes... In my wife's work at home experience there was some jealousy that she got to avoid teambuilding by default, while the office people were punished by having to attend. How come I have to go to the Christmas party on my day off and (VLM's wife) doesn't have to?

Oh and another jealousy issue... in this day and age not so many people smoke, but the smokers did not like that my wife could theoretically smoke at her desk but they can not (thankfully she doesn't smoke)

And discipline issues... "(VLM's wife) gets to pick up a sick kid at school without being formally written up for leaving work early because nobody notices, so why am I being written up?" and so forth. A lot of workplace BS exists so bosses can manufacture the reason to fire folks they can't just fire for no cause, and its going to collide with the obvious work at home differences.

At medium size corporations you can also run into Dilbertian requirement problems. Small corporations ignore "corporatism" and big corporations already have remote training, but it can be a mystery how to check the checkbox for annual diversity training, or annual PCI/DSS compliance training, or however else HR tortures the employees. She usually combined this kind of stuff with the rare facility visit, so we'll all go to diversity class as a team in the morning and then hang out and talk about work (aka goof off) in the afternoon.

Re: Remote Working – 3 Year Retrospective

#22

Nice writeup. I've noticed that a lot of the negatives (which the author nails, by the way) go away if you move the entire company remote. I've been working for the last 4 years with a 150 person software company that has no office whatsoever. Everybody is remote. As such, we get to remove the biggest land mine, which is being the "remote guy" on an otherwise onsite team, missing out on communication and finding your…

>It's the future. If you're not remote, find a way to fix that.

Would you suggest this even for new grads looking for a first job?

I just know that commuting every day is going to be incredibly depressing but I haven't seen much in the way of remote opportunities for fresh grads.

Re: Remote Working – 3 Year Retrospective

#23
post #6

On the "Substandard Treatment", my personal experience is the loss of power. I was the team lead for a government project. My wife took a job she always wanted; we move 900 miles away to Florida. Pretty much after that, while still team lead, the team lost cohesion. It was harder to drive changes and tasks at a distance than if I was in someone's cube.

I'm in a similar boat: remote team lead on a government project living in FL :)

Was the rest of the team local to each other? That can be difficult because the team may be accustom to conducting all communication verbally, where you need it to be electronic. I was a new-comer to the team when I became the remote lead, and one of the things I did was focus on getting folks to communicate electronically. Luckily for me, they were in individual offices spread around the building and two were in other buildings, so they were already using IM, chat, and email. I just needed to reinforce it.

Also from the beginning, I've focused on team cohesion and team communication. The team was in a bad state when I joined, so again lucky for me, it was something I knew needed extra attention. As a team lead, it's an important factor that you need to pay attention to, but perhaps don't have to spend a lot of time on when everyone is local. As a remote team lead, you need to spend a non-trivial amount of time on it.

And face time is still important. I travel twice a month for a day or two and try to meet with everyone during that time. I also conduct a daily standup where the rest of the team is in the room and I'm on the phone. It can be difficult to follow the conversations in the room from the phone, but really the goal is to make sure the team is talking to each other, and isn't about my control of the conversation or of the team.

Where in FL are you?

Re: Remote Working – 3 Year Retrospective

#25
post #6

On the "Substandard Treatment", my personal experience is the loss of power. I was the team lead for a government project. My wife took a job she always wanted; we move 900 miles away to Florida. Pretty much after that, while still team lead, the team lost cohesion. It was harder to drive changes and tasks at a distance than if I was in someone's cube.

I'm in a similar boat: remote team lead on a government project living in FL :) Was the rest of the team local to each other? That can be difficult because the team may be accustom to conducting all communication verbally, where you need it to be electronic. I was a new-comer to the team when I became the remote lead, and one of the things I did was focus on getting folks to communicate electronically. Luckily for me…

Have you tried doing a daily standup where everyone calls in individually from their office? In my experience things work the best when everyone is operating remotely with the same "communication handicap".

Re: Remote Working – 3 Year Retrospective

#26
I lead a 100% distributed team for a subsidiary of NYSE:KAR [US-based] and have worked remotely for 5 years. I think this post is very accurate - although we don't have a fancy video-conferencing system, good communication and skype are paramount to remote success (along with VOIP phones, wikis, github enterprise, email and rest of the usual suspects).

Additionally, it takes the right personality -- a self-starter who can work a dedicated day with minimal oversight. That means: not playing xbox in the middle of the day or running around taking your kids to soccer practice (though, a little of that is understood, just not blowing off 5 hours a day).

For me personally, no commute (did the bay area thing for years) and raising my kids where I want to is ultra important. Hope that more companies will realize the benefits of remote engineers. I agree with a comment made here re: lamenting the lack of skilled engineers, but not hiring remote. Rings hollow to me too.

(oh, and I'm hiring!)

Re: Remote Working – 3 Year Retrospective

#27
post #22

Nice writeup. I've noticed that a lot of the negatives (which the author nails, by the way) go away if you move the entire company remote. I've been working for the last 4 years with a 150 person software company that has no office whatsoever. Everybody is remote. As such, we get to remove the biggest land mine, which is being the "remote guy" on an otherwise onsite team, missing out on communication and finding your…

>It's the future. If you're not remote, find a way to fix that. Would you suggest this even for new grads looking for a first job? I just know that commuting every day is going to be incredibly depressing but I haven't seen much in the way of remote opportunities for fresh grads.

> Would you suggest this even for new grads looking for a first job?

Nope.

I've been a full-time remote worker for 6.5 years, and 1/2 time (2 days a week) for 4 years before that. During that time I've managed and hired remote workers.

The reality is remote work is not for everyone, and I think that is even more so for new grads. There is a lot of mentoring that happens early in someone's career, and that is difficult to pick up in a remote environment. I think over time the need for having that on-site mentoring decreases, but it's critical in the first 12 to 24 months.

Re: Remote Working – 3 Year Retrospective

#28
post #25

Earlier quoted context omitted.

I'm in a similar boat: remote team lead on a government project living in FL :) Was the rest of the team local to each other? That can be difficult because the team may be accustom to conducting all communication verbally, where you need it to be electronic. I was a new-comer to the team when I became the remote lead, and one of the things I did was focus on getting folks to communicate electronically. Luckily for me…

Have you tried doing a daily standup where everyone calls in individually from their office? In my experience things work the best when everyone is operating remotely with the same "communication handicap".

Yes I've tried both. It seems like a trade-off to me. Everyone now is completely into using electronic, asynchronous communication, following up verbal discussions with a quick email or IM listing highlights/decisions, etc. Imposing that handicap can help, but don't need to work on it so much anymore. Whereas getting everybody in the room for a quick status, a few jokes and good laughs, and some ranting about the customer seems to keep morale high. That non-trivial amount of time includes continuously assessing what is and isn't working.

Re: Remote Working – 3 Year Retrospective

#30
post #26

I lead a 100% distributed team for a subsidiary of NYSE:KAR [US-based] and have worked remotely for 5 years. I think this post is very accurate - although we don't have a fancy video-conferencing system, good communication and skype are paramount to remote success (along with VOIP phones, wikis, github enterprise, email and rest of the usual suspects). Additionally, it takes the right personality -- a self-starter wh…

Email address?
Post reply on HN