Live data from Hacker News

Working remotely is hard

moishelettvin.com

111–120 of 163 posts

Re: Working remotely is hard

#111
post #2

Working remotely is excellent. 1.5 hours less commuting - that's more time to get work done or go to the gym or read the news. No one can come to my desk to socialize or ask a quick question to fuck up my flow. No one requiring me to arrive at an office at an arbitrarily early time. No dress code. No ad hoc meetings in the conference room. Listening to music I like aloud. All conf calls done on speaker. I'm home to r…

My last 2 years as a remote worker (from east coast for a SV company) have been the most productive in terms of software output in my life. I've been able to focus on the task at hand very well, and have been given pretty free reign to work on some large projects crucial to the company's product.

The most difficult part was having to deal with a dead-weight VP of Engineering (my boss) who had no process, knowledge, who could not think on his feet in person or over the phone. I had to talk to the CEO and product management to understand the next evolution they wanted, and to actively thwart fruitless conversations and diversions from the boss. I asked for wikis, better bug-trackers, or other tools to better coordinate documentation and work. Finally, after a new CEO and after the VP Engineering was fired about four months ago, things have improved. We immediately followed through on Confluence (great wiki for organizing and documenting engineering and other efforts), JIRA (OK bug tracker), transitioned to git with Bitbucket. Communication and recording of designs, etc., has improved a lot. The new VP Engineering hired a month ago has improved things more -- he's rational, understands the technology, is good at organizing effort, and doesn't asked stoopid questions. I no longer venture into inappropriate and unprofessional phone behavior, which I resorted to many times previously out of frustration.

I regretted so many times joining the company, and knew from my initial interview discussions with the VP Engineering that I shouldn't have joined in the first place. The salary and options were too good to pass up, though, and the problem addressed was interesting enough. I also knew others in the company and thought it might be fun working there. I spent many late nights working on stuff for a boss who could not appreciate the magnitude of what was being requested and delivered.

I also spent many late nights repeatedly diagnosing scalability and performance problems that were not my own but rather in a few modules I had to invoke. Even after being presented with clear evidence in myriad in-house and customer cases this prior boss could not clearly grasp the urgency of fixing the issues. The issue was live at customer sites for over eight months before they were finally fixed.

So ...:

  - I miss SV friends after my move to the Southeast and haven't quite found "my people" here yet ... so I feel somewhat isolated

  - I work very effectively and don't take liberties with schedule, but I don't overwork either unless there's an urgent issue

  - I get to work from home or from a local coffeeshop, restaurant, or other venue -- I like this freedom

  - I get to do a lot of my daughter's events in daytime, nobody's looking over my shoulder

  - ... all these pros/cons were heavily dominated, though, by one big negative -- make sure you can get along with your boss, which wasn't my case

  - why didn't I jump ship?  it's hard to find another remote gig, and my terms were, I believe, pretty decent;  the company has a chance of doing something decent and being worth something -- largely due to product area, C-level reputation, good sales -- the product has some shortcomings that will eventually be overcome
[edit: minor changes, formatting]

Re: Working remotely is hard

#112
I believe I have a very good setup for working remotely. I have a house with a yard, and I can work indoors, or I can work outdoors (and regularly do.) The key, however, is that I work at a coworking space 2-3 days a week for part of my work day. It provides the perfect amount of social interaction, which I get to gatekeep. If I'm doing something particularly detail oriented, I stay home. If I can stand some interruptions, I head to the coworking space.

I don't know if all coworking spaces are as awesome as the one I have found myself at, but it fundamentally competes the "work at home" model for me.

Re: Working remotely is hard

#114
post #2

Working remotely is excellent. 1.5 hours less commuting - that's more time to get work done or go to the gym or read the news. No one can come to my desk to socialize or ask a quick question to fuck up my flow. No one requiring me to arrive at an office at an arbitrarily early time. No dress code. No ad hoc meetings in the conference room. Listening to music I like aloud. All conf calls done on speaker. I'm home to r…

I'm not a fan of people interrupting either, but I've come to realize it does help the team run more efficiently. If I get 3 legitimate interruptions a day where 5 minutes of my time saves the other developer an hour, overall it means my team just accomplished 3 hours of work in 15 minutes. Or say some error or urgent request comes up, it's been my experience at our office that the point person can look around, grab…

I switched from remote back to in-person about 2 months ago, and to be honest I'd completely forgotten how much easier it is to get some things done in a co-located environment. There were a lot of great things about working from home, but getting things done at anything above a "banging out the actual code" scale was not one of them.

I wish I could take back all my prior invocations of the complaint that someone interrupting me for 15 seconds eats 15 minutes of my productivity. Not only have I come to recognize just how transparently self-centered that meme is (and I'm embarrassed that I couldn't see it before, but given all the other great things about working from home I suppose a little confirmation bias is understandable), I've also realized that there are really quite a few domains where premature optimization is the root of all evil.

Re: Working remotely is hard

#115

At the risk of sounding totally ridiculous or trolly, the toughest challenge I've faced when adjusting to working remotely is answering the question, "When should I shower?" It's easy when you're working in an office job: Shave and shower before you go into work in the morning. When no one will see your face, you're suddenly left with the curse of too many options. In the morning? But what if your roommate needs the…

That part is easy. Shower after you work out, whenever that is.

Re: Working remotely is hard

#116
post #2

Working remotely is excellent. 1.5 hours less commuting - that's more time to get work done or go to the gym or read the news. No one can come to my desk to socialize or ask a quick question to fuck up my flow. No one requiring me to arrive at an office at an arbitrarily early time. No dress code. No ad hoc meetings in the conference room. Listening to music I like aloud. All conf calls done on speaker. I'm home to r…

I jog during the time I normally would be commuting, on nice days I work with the windows open, at the office I have a certain level of anxiety - just thanks to the traffic around me. I'm with you on this, working from home is awesome. It suits my personality.

Just a thought: you might someday find a home and work orientation where you can jog to work and shower there. This arrangement is certainly possible in cities like SF. Also many offices have windows that can be opened (if I were your colleague I would definitely want the window open if it meant something to you).

(It sounds like you are happy! I just wanted to point out to you and others that these two particular perks do not necessarily require working from home)

Edit: same general idea goes for the folks down thread appreciating access to a full kitchen. In fact, if one were designing an office, would this thread not be a great place to get ideas to distinguish your new office in awesome ways?

Re: Working remotely is hard

#117
post #23
post #14

Earlier quoted context omitted.

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

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.

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

#118
post #9

I believe remote work is one of the greatest advances of modern labor.

Wouldn't it be more accurate to say that on-site work was just a temporary regression? Back in the time where almost everyone worked on a farm, the farm was also your home, and mirrors a lot of what remote workers experience again now.

Re: Working remotely is hard

#119

Funny. I work at a company that has two work-from-home days. Those two days are, hands down, the most productive days my team has all week.

Have you thought it might be because of the planning and preparation done on the other 3 days?

It is like the person who skips a meeting to be 'more productive' and then has to go around bothering everyone to understand the decisions made in said meeting.

Re: Working remotely is hard

#120
post #47
post #2

Working remotely is excellent. 1.5 hours less commuting - that's more time to get work done or go to the gym or read the news. No one can come to my desk to socialize or ask a quick question to fuck up my flow. No one requiring me to arrive at an office at an arbitrarily early time. No dress code. No ad hoc meetings in the conference room. Listening to music I like aloud. All conf calls done on speaker. I'm home to r…

I've found, after coding+managing remotely[0], that it takes a specific set of traits to be a successful remote worker. - strong work ethic: no one needs to tell you that it's time to start working for the day/after lunch etc. - strong communication: not the same as being an extrovert. might even help if you are an introvert. Just comfortable with text being the dominant means of articulation. - strong 9-5 boundaries…

Why the 9-5 boundary? Personally, I get my best work done during non-traditional hours, e.g. past midnight.
Post reply on HN