Live data from Hacker News

Why I Only Work Remotely

medium.com

111–120 of 191 posts

Re: Why I Only Work Remotely

#111
post #58

Earlier quoted context omitted.

Wouldn't generalize as much but point taken. Frankly,my project pays well enough and it is remote too but what really makes the pay great in my case is a no income tax state for me. Otherwise the pay would be meh if I had to shell that out.

I don't think most state income taxes are that burdensome. My state's is 3%, so on a $100,000 salary not considering any deductions, the difference would only be $3,000 between my state and a non-income tax state. If you were making $200,000, it would still only be $6,000. Neither amount is peanuts, I realize, but it's not the difference between good and meh either.

Here in NYC state income tax is ~6.65% and city is an additional ~3.648%. So about 10k on 100k or 20k on 200k.

Re: Why I Only Work Remotely

#112

Richard Hamming said [1] it best: Another trait, it took me a while to notice. I noticed the following facts about people who work with the door open or the door closed. I notice that if you have the door to your office closed, you get more work done today and tomorrow, and you are more productive than most. But 10 years later somehow you don't know quite know what problems are worth working on; all the hard work you…

You can't keep your door open in an open office because you have no door.

Re: Why I Only Work Remotely

#113
post #64

A question to all of you who only work remotely, and I'm sure it's been covered by HN so forgive me, but where do you find reliable work that's remote? I can see getting lucky maybe and scoring one maybe two gigs that allow remote but a caterer doing it? When my wife's gig is up she would love to work from home. She already works from home two days a week. But she has no idea how to make a career out that reliably. S…

I only work remotely, but it does really limit the pool of available work. Weworkremotely.com is a good resource.

Re: Why I Only Work Remotely

#114

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…

> Having worked on several teams where some members were in completely different locations (and time zones), I never want to experience that again. Give me every person relevant to my work in the same physical space; I don't want to get blocked from doing my work because you've gone dark on slack.

If the office is online, going offline means leaving the office. There's a WORLD of difference between a meeting when 5 people are in an office and 5 are online, and a meeting when 10 people are all online. When everyone is online it works about as well as an in person meeting, and frequently better because conversations tend to be more direct.

That said, having no personal rapport can be a big problem on remote teams - were I to set one up there would be minimum quarterly physical meetings, with most of the purpose being to socialize and sync on new models rather than sit and do normal work.

Having 1-1 vidcalls just to "work together" has been very nice as well. Once you get out of the idea that a video call has to be a meeting I'd say you can get 95% of the way to a physical space. Does not work for every engineer however.

Re: Why I Only Work Remotely

#115

I agree with every word of this article and after 25yrs experience as a developer I have all similar experiences. Being a computer programmer is about the same as being a 'writer' (book author), and no one expects an author to sit with other authors in a special building to be able to write. With modern technology, and the wastefulness of time and energy spent commuting, there is just no longer any reason for a progr…

Most books don't require 10-100 authors, each focusing on the paragraph that they are experts in, needing to hold the pages together with APIs that are agreed upon by all co-authors. The collaborative aspect of a software project is much greater than that of a book. Yes, there are books that have a multiple of co-authors, but these co-authors tend to not operate lone-wolf.

There are different models for joint authorship. Some are pretty course-grained. In a lot of cases even if the writing used is pretty collaborative, one author does a final editing pass to come up with an integrated end product. From what I've seen, "collective ownership" models mirroring current fashions in software development remain relatively rare.

And while some software projects do need 100 people, most don't -- and most don't even need 10. I get the feeling that a lot of project managers don't even think about the possibility that something could be built by a focussed individual working in a low-distraction environment.

Re: Why I Only Work Remotely

#116

Earlier quoted context omitted.

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

That's a fair point. But in my limited sample size, there are plenty of companies that at least for a few years function just fine with full remote.

Re: Why I Only Work Remotely

#117

Earlier quoted context omitted.

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

Do none of those companies utilize chat?

My experience with "open office" arrangements is that most of the conversation (important and casual) takes place in chats anyway--even between people sitting right next to eachother--because generally people don't want to distract uninvolved parties.

Re: Why I Only Work Remotely

#118
post #68

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 agree with you. I personally am much more distracted at home because "I'm home". When I'm at work, I'm in work mode. I also find that I solve a lot of yesterdays roadblocks during my commute (20 mins each way) and the shower. Solving problems is not always about characters per second of new code. Over the years, I can't even count the number of times that I heard a conversation taking place and was able to step in…

I've worked remote full time and am now in an office full time with occasional work from home days.

The difference between having a dedicated home office "space" to do/think about work and just going to the "home" space and trying to get work done is night and day. Occasional working from home is completely different than full time working at home. Once you've carved out a good space and have reduced distractions outside of work space (say a spouse asking you to do chores) you can maintain work mode the entire time, sometimes even better than at work. The sense of control is amazing for getting hard stuff done and concentration.

There's something to be said for transition time though. My routine was that I would always leave the house whenever I was done with work, whether to go get groceries or go to the gym, or just go for a 10m walk. I can't cognitively switch from work things to home things in the blink of an eye, I don't think the hardware we have allows for that.

Re: Why I Only Work Remotely

#119

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…

The US has enough empty/low-density land in it that every metropolis west of the Appalachians could be shadowed by completely new cities, with other approaches to planning and density beyond just building around the ubiquitous automobiles. Then people and businesses can just gradually move in.

This is something that China has apparently been doing for a long time, albeit with insufficient attention to quality control. They occasionally get buildings that have high-tension power lines running through the stairwells, or buildings that just suddenly fall over, and then the West points and laughs. But at least they are making gestures towards urbanizing their rural populace, and re-urbanizing their existing urbanites. As useful as planning is, at some point you have to actually start building, or you never get anything done.

But then again, looking at the sort of development effort invested in Olympic Villages, where a huge, concerted effort puts up a lot of new construction in a short amount of time, putting up whole cities at once can also turn into an embarrassing disaster rather quickly.

In the US, it just seems like city governments are holding the city infrastructure as hostage to squeeze some more ransom money out of the residents, then shooting the hostage anyway. It's very frustrating to watch in other cities, and absolutely infuriating in your own. How much would it cost, really, to abandon an old, sprawly city, and build something that starts with a bunch of solutions to well-known urban problems that can't even be implemented when there's already a city in the way?

Re: Why I Only Work Remotely

#120
>It’s the same reason that communism does not work nearly as well as capitalism — things work best when you give people freedom as individual actors.

You said "capitalism" but you meant "liberalism," and you said "communism" when you meant "authoritarian dictatorship."

But setting aside this equally unnecessary and inaccurate argument, the whole tone of this article seems to glorify the archetype of the "110%" employee. I'm "passionate" about programming and computer science, but I also don't just want to pull up a JIRA and bang away code.

Even if we accept the author's premise that open offices and social work environments are bad for productivity (which many people here have already pushed back against), I didn't try to find a job with lots of smart people so I could only interact with them via email. Sure, an open office occasionally distracts me and gets me out of the "flow," but it's almost always to help someone or join an interesting conversation. These things are valuable to me on their own, because (1) I like interesting conversations and (2) it means I can ask someone for help whenever I need it. And that's a better long-term feeling than slamming out code every day, which, by month two or three, starts to feel a little uninspiring.

Post reply on HN