Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google’s Internal Data Show Engineers Found It Harder to Code from Home

theinformation.com

Post reply on HN
Print view View original

101–109 of 109 posts

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#101

Post by UncleOxidant »

bicx wrote: post #14

I think the key with working from home is learning to set up and maintain boundaries between home life and work life. I was working from home fulltime for well over a year prior to the pandemic. Prior to that, I went into an open office every day for about 10 years. Overall, if you subtract the time from a 1-hour round-trip commute, distractions from coworkers, and longer lunch breaks I had while going into the offic…

Doesn't the blurring of boundaries tend to work both ways, though? Meaning that, sure, you might be running an errand during the middle of the day, but you might also keep working well past your normal quitting time when you were in the office.

> Let's also not forget that 2020 is a steaming pile of shit, and it's had more horrific distractions than any year in recent memory.

I think that this is probably the bigger reason for any productivity hit that might be happening. Let's see how things are after the election (actually, after the inauguration) and after covid is in the rear-view mirror.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#102

Post by jeppesen-io »

I tried working from home for the last six months. I've tried everything recommend here, nothing worked. Productivity tanked

Recently the office opened up, just for me. I'm alone in the office but massively more productive

I find it frustrating that so many comments discount that some people just don't work well from home. I have no logical reason, but I just need to get ready, walk to work to get stuff done

WFH may work for some, but it does not work for me no matter what I do and I'm sure it's true for others

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#103

Post by quaffapint »

bicx wrote: post #39
DoofusOfDeath wrote: post #34

I've worked from home for about 6 years, with varying levels of success. But I've been surprised by how much I'm thrown off by having my kids home during the school day (remote learning because of covid). Even with a decently soundproof office. It just prevents the house in general from being calm and quiet during my peak work hours.

I am honestly concerned that I may be getting chronic ear issues from wearing noise-cancelling headphones constantly. Knowing that your family is right outside the door (and vice versa) is extremely challenging.

Oddly enough I was worried about the same working from the office with its wonderful open office layout.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#104

Post by tzs »

bicx wrote: post #14

I think the key with working from home is learning to set up and maintain boundaries between home life and work life. I was working from home fulltime for well over a year prior to the pandemic. Prior to that, I went into an open office every day for about 10 years. Overall, if you subtract the time from a 1-hour round-trip commute, distractions from coworkers, and longer lunch breaks I had while going into the offic…

Maybe get an analog chess clock, like this [1]. If you want to work 8 AM to 5 PM, set one side of the clock to 8 when you start work and start that side. Let's call this side of the clock the "work" clock.

When you stop work for something that you would not have stopped for if you were not working remotely, stop the work clock. Start it again when you resume work.

Work until the work clock reaches 5.

This might help in a couple ways.

1. It will make you more aware during the work day day how much time you spent so far on non-work stuff. That may make it easier to do things like help your wife or run errands without inadvertently doing so many of those things on the same day that you don't get enough work done.

2. When you do stop work to do something else, knowing that you'll make up the time later that day might make it more guilt free.

[1] https://www.amazon.com/BETTERLINE-Professional-Analog-Chess-...

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#105

Post by cvhashim »

tzs wrote: post #104
bicx wrote: post #14

I think the key with working from home is learning to set up and maintain boundaries between home life and work life. I was working from home fulltime for well over a year prior to the pandemic. Prior to that, I went into an open office every day for about 10 years. Overall, if you subtract the time from a 1-hour round-trip commute, distractions from coworkers, and longer lunch breaks I had while going into the offic…

Maybe get an analog chess clock, like this [1]. If you want to work 8 AM to 5 PM, set one side of the clock to 8 when you start work and start that side. Let's call this side of the clock the "work" clock. When you stop work for something that you would not have stopped for if you were not working remotely, stop the work clock. Start it again when you resume work. Work until the work clock reaches 5. This might help…

Thank you, this is a great idea. I’ll look into the chess clock.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#106

Post by rweir »

alisonkisk wrote: post #89
Waterluvian wrote: post #49

Imagine if the future of the FAANG style interview focused on how good you are at working from home. I wonder it the outcome would be frustratingly different for many of those who are not too great at it. I think we should embrace WFH but not wholly adopt it as the one and only way people are effective at their job.

They haven't substantially changed the interview format in 20 years; I doubt they'll change now.

they got rid of stupid puzzles at least.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#107

Post by stolenmerch »

I am one of those engineers that finds it harder to code from home. Some of the initial problem was that we were given a one day notice to pack up and stay home for the foreseeable future. It was not a choice and I wasn't prepared. Part of the problem is that I don't have the space in my house for my children, my spouse, and myself to have anything close to a "home office". As it stands, I am resigned to work on a 13" Macbook from a recliner in my living room after being accustomed to my dual monitors, standing desk, and keyboard at work. I'm sure I could set this up at the coffee table, but that seems almost worse and also so long work/life separation. On top of this, I was in a very healthy groove of hitting the gym every lunch hour, which helped my productivity tremendously. Sure, I could do burpees in the living room or something, but it's not happening.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#108

Post by taylodl »

Our experience has been the opposite - our productivity has measurably improved since our team started working from home and that's been the experience of most of the teams in our organization. It's been so successful in fact that our management is now looking to make this a permanent arrangement. It's a win-win situation: the teams are more productive and there's an opportunity to reduce facilities costs.

Re: Google’s Internal Data Show Engineers Found It Harder to Code from Home

#109

Post by ix101 »

UncleOxidant wrote: post #101
bicx wrote: post #14

I think the key with working from home is learning to set up and maintain boundaries between home life and work life. I was working from home fulltime for well over a year prior to the pandemic. Prior to that, I went into an open office every day for about 10 years. Overall, if you subtract the time from a 1-hour round-trip commute, distractions from coworkers, and longer lunch breaks I had while going into the offic…

Doesn't the blurring of boundaries tend to work both ways, though? Meaning that, sure, you might be running an errand during the middle of the day, but you might also keep working well past your normal quitting time when you were in the office. > Let's also not forget that 2020 is a steaming pile of shit, and it's had more horrific distractions than any year in recent memory. I think that this is probably the bigger…

The economic uncertainty is quite likely to be a motivator more than a detractor. I.e. remote teams are keen to prove they are working highly effectively in order to prevent being near the top of the list if the company is forced to down-size.
Post reply on HN