Live data from Hacker News

Why I Only Work Remotely

medium.com

41–50 of 191 posts

Re: Why I Only Work Remotely

#41
post #9

At home I can control the noise & temperature of my work environment. These aren't brought up often but they're huge to my productivity. I can't work well when I'm uncomfortable. Trying to code with numb fingers or while sweating is miserable to my productivity.

My home office has a $3000 computer, $600 chair, high end keyboard and mouse, a huge 4k screen. My office temperature is at the optimal for my body and my setup is positioned according to the sun coming in the window.

At work it usually* is a $600 computer, a $60 chair, low end dirty keyboard and mouse, small low quality screen. The office is cold, I have glare in my screens... and I share a room with 60 persons.

It's hilarious how my personal setup outclass my professional one.

* I am lucky enough to have found an employer which value his employees and that's not the case right now for me.

Re: Why I Only Work Remotely

#42

I rarely work remote even when I have the opportunity to do it; I'll explain. The author seems to have a single-mindedness about optimizing their own performance. If performance in terms of your value to the business was about sitting down at a computer and coding, getting in a "flow" state, etc, I would agree. Problem is, personal efficiency doesn't necessarily align with value generated. I've seen engineers spend m…

I don't get you. What does a developer has to do with deciding what the business needs? If your job is that, ie, figuring out what a business needs, then by all means work closely with people..But I am not sure that is the type of work being discussed in this context.

If your job is doing exactly what you're told to do, and nothing else, then you'll find that you are very replaceable.

Re: Why I Only Work Remotely

#43

I rarely work remote even when I have the opportunity to do it; I'll explain. The author seems to have a single-mindedness about optimizing their own performance. If performance in terms of your value to the business was about sitting down at a computer and coding, getting in a "flow" state, etc, I would agree. Problem is, personal efficiency doesn't necessarily align with value generated. I've seen engineers spend m…

I think we'll have to agree to disagree here. If you're heads-down on a project and it's not contributing to the value of the product, there are other issues with your business than remote-v-office culture. If pivoting your engineering goals requires hallway conversations, there's something wrong. To be sure, not everyone is cut out for remote work, the same way not everyone is cut out for office work. For my part, I…

> If pivoting your engineering goals requires hallway conversations, there's something wrong.

I agree but isn't there always something wrong?

I'm in that spot, I worked mostly remote for the past 4 years and at every company it would have helped a lot to have a casual hallway conversation from time to time.

It shouldn't be necessary but in reality it often is. It seem to me like you need well thought out, light weight processes to make this work. I think it should work, but I never saw it working myself..

Re: Why I Only Work Remotely

#44

I feel that gigantic metropolises are not optimal environments for software engineering. NYC, and it's helter skelter of noise and traffic and garbage and tiny living spaces, in my humble experience and opinion is not conducive to hard engineering problems. I am probably completely wrong here and just a hopeless introvert with an axe to grind, but from my experience, working in home offices in towns like Boulder, Col…

> I think the future of work will be semi-distributed, and this mad consolidation into a few coastal cities will be seen in the future as a gross inefficiency.

I disagree with this prediction.

1) If given the choice, most people would prefer to walk to their day-to-day destinations rather than drive.

2) In order to create an area in which most destinations are within walking distance of the residents, a certain level of density is needed. This level of density manifests itself in "the traditional city", ranging from the relatively low traditional density San Francisco Mission district (25k ppl/sq mi) to the medium density neighborhoods in Brooklyn (for example, my neighborhood, Bedford-Stuyvesant, has a density of 57k ppl/sq mi. Williamsburg is similar) to ultra high density Manhattan areas, such as the Upper East side, which supports a population density of 120k ppl/sq mi (!!!). Older European cities are often within these density bounds.

Less density than the Mission and other forms of transportation become necessary for day-to-day tasks, and the city's face starts to resemble more driving-oriented (midwestern) cities.

3) In order to go beyond one's immediate neighborhood, quality public transit is important, as owning a car is an extreme unnecessary expense if the neighborhood is truly walkable.

4) Very few walkable metropolitan areas exist in the USA today, as transit is insufficient and neighborhoods are sparsely populated relative to a traditional city. Most that do are historic urban cores: for example, I'm writing this reply from Downtown LA, which appears visually similar to parts of Manhattan, is relatively walkable, and has decent transit options, but not nearly on the level of NYC.

5) Since so few desirable, walkable metropolitan areas exist with sufficient public transit, the ones that do featuring housing that is either extremely expensive (supply/demand) or, as mentioned, poorly maintained/insufficient. This forces the vast majority of people to live much further than walking distance from their workplaces -- often up to an hour or more away -- if they want to live in a pleasant apartment in a pleasant neighborhood within their means.

6) The result is that (due to shipping, coastal) cities predating cars are the only ones that can offer this living experience, and you will pay considerably for the privilege of walking to the bodega at 3 AM while extremely intoxicated, saying hello to the friendly person behind the counter, and buying a gatorade before you pass out in your 8'x10' bedroom.

-----------------

NYC had a chance to remain at least somewhat affordable (by building transit options when acquiring right-of-way in undeveloped Long Island and Queens from the 30s thru the 60s), and Robert Moses completely blew it (because of his personal hatred of minorities and poor people). If you want to find out more about that particular topic, I suggest you read Robert Caro's book "The Power Broker".

One idea espoused in the book is that when you build mass transit before you build the community, you end up with a medium-to-high density community. When you build highways before you build the community, you end up with a low density community. These community patterns are nearly impossible to change -- this is why people complain Los Angeles builds "trains to nowhere" -- the existing communities are low density, but medium density is a prerequisite for a train line to be useful to sufficient numbers of people.

The only way to fix this in the future is to build cities with this idea in mind (or, alternatively, pray that self-driving cars fix everything). Redevelop existing areas to support new transit (an older Uber driver pointed out to me multiple new, high density developments in downtown LA, and suggested they were helping improve the area's safety and commercial diversity). Urban areas don't have to feel like NYC, but we chose a path back in the 1950s whose ultimate result was to dissolve the communities and lifestyles necessary for individual human happiness.

Looking forward, I'm seeing this "mad consolidation into a few coastal cities" become a "consolidation into a larger number of smaller cities" considerably more dense than Boulder, CO, and we will see this redevelopment of urban cores as a sign of what's to come.

Re: Why I Only Work Remotely

#45

Earlier quoted context omitted.

I don't get you. What does a developer has to do with deciding what the business needs? If your job is that, ie, figuring out what a business needs, then by all means work closely with people..But I am not sure that is the type of work being discussed in this context.

> I don't get you. What does a developer has to do with deciding what the business needs? If your job is that, ie, figuring out what a business needs, then by all means work closely with people..But I am not sure that is the type of work being discussed in this context. Well, if you're a rank and file engineer, your "job" isn't explicitly to figure out what the business needs. However, if you care about becoming more…

This is the fundamental difference between great engineers and the rest. Just giving a damn and being engaged. Seriously.

Re: Why I Only Work Remotely

#46
The main problem I see with this article is the author is totally focused on himself. If you are a solo developer this is fine, but if you are part of a team then his attitude is detrimental.

I work as part of a team and we all work remotely most of the time, but we work the same hours because working different hours would cause problems. It's hard to conduct a daily stand up if everyone's working weird hours. We have some flexibility for people but everybody has to be around for the 9:30 stand up. This helps with coordinating of larger projects and bringing up blockers which the PO or Scrum Master can remove.

If some lone developer is working 3pm to 11pm then that person is not really coordinating with the rest of the team.

Also I'd really hate to hear what this guy thinks of pair programming.

Re: Why I Only Work Remotely

#47

I rarely work remote even when I have the opportunity to do it; I'll explain. The author seems to have a single-mindedness about optimizing their own performance. If performance in terms of your value to the business was about sitting down at a computer and coding, getting in a "flow" state, etc, I would agree. Problem is, personal efficiency doesn't necessarily align with value generated. I've seen engineers spend m…

There are the notions of:

o clear written requirements expressing the business and high level technical needs.

o well defined acceptance test procedures to ensure that the delivered software (or hardware or whatever) meets those requirements

o thoughtful partitioning of the work between team members to minimize the needed communication and enable the team members to focus and work on their part without having a committee meeting every few minutes on every minor issue.

None of these are new practices. They, or something similar, is needed to work effectively remotely or for that matter in quiet offices with closed doors.

Re: Why I Only Work Remotely

#48

The time to travel to the office is often ignored too (it sounds lazy to even mention it because it's the norm). If you're working remotely and it takes 30 mins to get to the office, you're at an absolute minimum burning 5 hours a week going back and fourth from the office when you could be doing something else. Add in the extra time changing to and from work clothes, and having to leave the office to get food instea…

I actually enjoy my commuting time. I listen to podcasts or think about what I need to do when I get to work (or home). If I'm on my bicycle, I find that my mine really wanders and I enjoy that.

Once I'm at work, I get down to it and am good for about 4 hours or so (on good days) of really good work. Spend an hour or two on email, light reading, talking to coworkers, and that's my day.

Re: Why I Only Work Remotely

#49
post #9

At home I can control the noise & temperature of my work environment. These aren't brought up often but they're huge to my productivity. I can't work well when I'm uncomfortable. Trying to code with numb fingers or while sweating is miserable to my productivity.

My home office has a $3000 computer, $600 chair, high end keyboard and mouse, a huge 4k screen. My office temperature is at the optimal for my body and my setup is positioned according to the sun coming in the window. At work it usually* is a $600 computer, a $60 chair, low end dirty keyboard and mouse, small low quality screen. The office is cold, I have glare in my screens... and I share a room with 60 persons. It'…

Have you ever thought about buying your own keyboard, mouse, monitor, and chair?

Re: Why I Only Work Remotely

#50

I feel that gigantic metropolises are not optimal environments for software engineering. NYC, and it's helter skelter of noise and traffic and garbage and tiny living spaces, in my humble experience and opinion is not conducive to hard engineering problems. I am probably completely wrong here and just a hopeless introvert with an axe to grind, but from my experience, working in home offices in towns like Boulder, Col…

Thank you, Boulder, CO Chamber of Commerce.
Post reply on HN