Live data from Hacker News

Ask HN: What's your experience with remote working? as employees/employers?

news.ycombinator.com

21–30 of 101 posts

Re: Ask HN: What's your experience with remote working? as employees/employers?

#21
I was able to work remotely (exclusively) for 2.5 years from 2004-2007. I was able to live in two different, beautiful places, and moving was a non issue. My work schedule was totally random - I would wake up whenever I wanted and simply skip "work" days at random going to hike, but despite this it was, in terms of output, one of the most productive periods of my life.

However, after that period I simply decided to quit, because of the totally absent social life. Now I waste 2 hours a day in commute and waste time in useless meetings setup by some random executive. I'm also paid less comparatively, and have more expenses. I still wouldn't go back. I now discuss openly and face-to-face with great colleagues, work with great problems together, share great ideas, etc. Choosing a good job is so much more important.

I would still happily work remotely one, two days a week. Just for the convenience. Or maybe in small periods throughout the year. Still, I will never work remotely again.

During the period I worked remotely, I was able to knew/meet a lot other people that worked remotely all the time (some since the '90!). We all had, more or less, the same problem: we all scored incredible amounts of hours (compared to normal workers) despite the absence of both work pressure and schedule. We tended to be a bit extremists in quality (of course, you had all the time to think about the best solution), which wouldn't work well with normal colleagues that had to struggle with time constraints. I didn't understand that at the time. Because of your derailed work schedule, you generally tend to be less social even if you have good social contacts. In the end it's a self-inflicting problem: you are less active socially, you dedicate more time to your work, etc etc. It's actually quite difficult to find balance. I couldn't in the end.

Employers should take note, because working remotely sorta-implies a very dedicated person. Being able to work without any social pressure is difficult if the worker is not a motivated person. Un-motivated persons will basically quit by themselves after just weeks (I saw it happening a lot).

It also boggles my mind that employers (and this happens mostly in EU) still don't grasp that concept. Regulating work hours, presence, etc is stupid unless your job is depending on a regulated schedule itself. People slack right in front of the monitor all the time. Allowing people to work from home it very beneficial: it actually increases the production (less time wasted in commute, colleagues, etc). But of course, it really depends on the people that you hire, and how willing are you to thrust these people.

Re: Ask HN: What's your experience with remote working? as employees/employers?

#22
I have worked remotely for 6 years - in one case working for a UK company and living in Australia. Once you get the hang of it (especially as an engineer) it is significantly more productive. BUT it does take the right sort of mindset - I am self-disciplined in terms of starting hours, I do not get distracted by things around me.

Of course the downside though is that the work/life line gets significantly blurred. At least working at a office when finishing work I 'finished' working remotely it doesn't work like that.. just will finish this one last thing then I will stop... and I don't.. I have a family now so its great to be near to see them grow up... but sometimes families still don't get the fact you are 'working' can you just drop so and so off to school etc...

Re: Ask HN: What's your experience with remote working? as employees/employers?

#23
I've worked as a (semi-)remote employee for the past 2.5 years for a HUGE multinational software company. Here's a braindump of experiences:

- I work in Ireland and my colleagues are in the US. The time zone difference is generally handy because I can work in the mornings and they come online around 1:30pm. So my afternoons (or their mornings) are when meetings and scrum calls happen. I don't attend any meetings outside my core work hours, and I'm rarely even asked to. I'm not sure a wider timezone difference would be suitable

- I actually work from a subsidiary office so I have people to get lunch with, even though I don't have any work contact with them.

- Things are usually scheduled around a US working day so, for example, nightly builds were scheduled to run in the early morning so they hadn't finished by the time I started work. And then I'd be trying to download them just as the corporate network start to get saturated by the US employees starting work.

- My line manager is here in the office but functional managers are in the US. This creates odd situations where I can phone-in sick but my teammates don't get informed. Or where my annual review is done in the US but the salary/bonus must come out of an Irish budget.

- "Ramping-up" on the product was pretty hard because if I got stuck in the mornings I had to wait until the afternoon to get some answers. Once that product learning curve is over and you become more autonomous it's much easier.

- There can initially be some resentment from US employees that their jobs are going to Ireland (an uncomfortable truth) and it can be difficult for me to know that an experience engineer has been "resource actioned" because I'm - Many of my US colleagues are also remote / working from home but this is actively being discouraged. If fact, we all (US in-office, US working-from-home, and me in Ireland) had to attend a rather tactless meeting which listed the disadvantages to remote working: poor career progression, no management visibility, loneliness, poor team cohesion, communication problems etc. It's not like this was my choice!

- Tools: primarily email, instant messaging and regular conference calls. We also have get defect and version control notifications by email.

- I think things would be easier in a non-corporate setting because we'd have the flexibility to choose better tools: something campfire-ish, Git, some visual story planning / Kanban board, perhaps video conferencing over Skype, ambient webcams so you can see each other etc.

- I'm not sure if I'm a typical programmer: I dislike making phone calls and generally prefer to talk face-to-face with people. You get to pick up on subtle little clues (are they bored? are they stressed? are the busy? are they saying yes but only reluctantly?) which are lost in non-visual mediums.

Edit: I work in a very quiet open-plan office and this makes phone calls much harder. Ideally remote workers should have a private office so they are comfortable speaking on the phone. Particularly important if you want to conduct annual reviews over the phone!

- Having said all that, I'm seriously considering moving into remote freelancing or trying to find a permanent remote position but most job sites are focused on location-centric jobs. Any good pointers?

Re: Ask HN: What's your experience with remote working? as employees/employers?

#24

I'm an employer. Quick background: We're a small Django consultancy/web app development company based in the UK. 7 people, all remote, split as three developers, one frontend dev, one designer, one sales, one administrator. I'm a developer/managing director. Our experience with remote working has been largely very positive. - It keeps our overheads very low. I think that when we remove our staff wage bill, our operat…

how do you convince your clients if you don't have physical "centralized" location?

i think it depends on the culture, but in here (asia) people will hesitate doing business with a company with "scattered" team.

Re: Ask HN: What's your experience with remote working? as employees/employers?

#25
post #14

I am a remote cakephp developer from the Philippines. I have been at the most productive stage of my career. I do invest to make my work the highest possible quality. A home office so I can concentrate, I buy new equipment (iMac 24") and I have two internet connections. My main problem right now is getting burned out. I stay at home most of the time and it is quite depressing sometimes.

Haha, I'm in the Philippines also and I understand the need for two internet connections. Now if only I could hook up two electrical connections. Oh well, I guess I need to pick up a generator. I have a fully self contained development environment on my USB drive for when I absolutely can't deal with down time during internet connection / electricity outages. Then I can just grab any computer at an internet cafe and…

I'm from the Philippines too (Taguig), and when I was just starting I was paying for 2 connections. Right now I just maintain one (dsl), and during outages and other emergencies I go to cafes with wifi. Generally I try to work on a cafe once a week to minimize the isolation.

Re: Ask HN: What's your experience with remote working? as employees/employers?

#26
i work for american companies from abroad (i am english, but live in chile). i have worked for a small-ish startup (about a dozen employees) and a technical consultancy (similar size). before that i had worked with a team split across two locations (usa and chile); before that i worked from england for a company in scotland (after working locally - moving south pushed me into my first remote job).

i am not convinced that the problems are any worse than working locally, to be honest. the problems may be different, but it's still true that a good manager makes life easier, and that a bad manager can be worked around.

so i would say that if you have an experienced employee that you trust (as i hope i am!) then it's not a big deal. and inexperienced people that you don't trust are still a crap-shoot - remote working doesn't change that.

any way of working has its own issues. if you're competent you can solve them; it's your job to do so. if you can't, working locally will only make the misery local.

i guess maybe people want specific advice anyway. the most important thing is that you (as employee) need to force feed status to your employer. there's no feeling worse in the world than hearing "so what have you been doing?". meeting up physically once a year or so is also a good idea. weekly teleconferences help. that's all as obvious as it sounds, which brings me back to my original point...

[ps and personally, i love it. the peace and freedom are great. good pay (compared to local market) is a bonus.]

[pps an observation that might be illuminating - i just realised that half my computer screen is devoted to communication. i have a text console on the left, with (ascii) mail in the current tab; on the right i have an open chat window; in the middle is eclipse). the web browser alt/tabs over eclipse and chat.]

Re: Ask HN: What's your experience with remote working? as employees/employers?

#27
post #7

Working as a data scientist with a remote boss: communication was much more difficult. No telephony or software solution came close to standing on front of a shared whiteboard. Which sucks, because I really wish it did. Maybe what we need is actual The biggest win I've seen is with ops teams. I hope I'm not betraying any confidences, but a previous employer had an international ops team so as the americans were going…

There must be a share whiteboard app for iPad/Android?

Re: Ask HN: What's your experience with remote working? as employees/employers?

#28
post #2

I work remotely as a freelancer and my experience has been nothing but awesome. I'm from the CET timezone and the people I usually work with are either in PST or EST so there's a 6 to 8 hour time difference. Here are some of the benefits I've observed: - I'm a night owl, so I can directly communicate with the people paying me - even though I like long mornings, I still have at least 5 hours to work before employers w…

> * (locally I've been smashed into teams still on svn ... on new projects)*

Completely off topic, but: is this necessarily bad? Does the world stop when there's a centralized source control server?

I'm in an environment too where people are sometimes reluctant to move to newer, better software (svn is an example, our bug tracker sucks too), simply because of the learning curve / overhead involved. I started out by being annoyed with this, until I realized that at the same time using modern SW development practices is really what matters (e.g. a lot of TDD, BDD, MDSD here). I can survive svn, but I can't survive the waterfall model.

Re: Ask HN: What's your experience with remote working? as employees/employers?

#29
A few years a go I co founded start-up in the US while living in the UK. The other two founders both lived in the west coast, and I worked remotely. In the beginning it was fairly straight forward as it was only the three of us and another contractor from Russia. I developed the app, the contractor developed a component we needed and the other two were busy getting the business side together. When we got funded things got more serious as suddenly our little startup became a bigger company with offices and employees etc. I would basically do a 9-6 work day, and the Americans would clock on at around 5-5:30PM. We'd have a little overlap to talk about what's new over skype and I'll clock off. That was the theory of it but in practice I ended up chatting to them on skype at various hours as they sometimes needed information from me. This worked OK for me but I personally like being in an office and interacting with people. You become a recluse when you spend your days cooped up at home. Having said that, today I still try to do at least one day of home working to keep a balance between home and office.

The main problem I found in remote working are distractions from family, kids etc (who forget you're physically at home but mentally you're not), and a side effect to that problem is that because you sometimes get gaps in your workday you end up stretching the day into the night, blurring the boundary between home and work time.

Re: Ask HN: What's your experience with remote working? as employees/employers?

#30
post #2

I work remotely as a freelancer and my experience has been nothing but awesome. I'm from the CET timezone and the people I usually work with are either in PST or EST so there's a 6 to 8 hour time difference. Here are some of the benefits I've observed: - I'm a night owl, so I can directly communicate with the people paying me - even though I like long mornings, I still have at least 5 hours to work before employers w…

How did you get started? Since you're not local, I'm curious about how you found your first clients in the US.
Post reply on HN