Live data from Hacker News

Nearly 40% of software engineers will only work remotely

techtarget.com

271–280 of 411 posts

Re: Nearly 40% of software engineers will only work remotely

#271

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

> I could be convinced to commute to a satellite office that's not affected by rush hour traffic. This right here. If I could get to work and back in 5 minutes I wouldn't mind the commute, ever. Unfortunately everyone wants to have offices in some downtown area, instead of just near a major city in a quieter part of town, safe back-roads that wont bother anyone.

This only works if they put the office in the quieter back-road section near you. Otherwise you're driving all the way across town. The last company I was with I talked with the owner and he was clear why they chose downtown - yes, it sucked, but it sucked pretty equally for everyone.

Downtown is also the place with the most transit going to it - you're excluding anyone who doesn't/can't drive if you choose to build in a quiet section.

Re: Nearly 40% of software engineers will only work remotely

#272

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

My father was a chemical engineer. Back in the 60s & 70s, the company would pay to relocate our family to wherever they needed him (this included purchasing the house if we didn't sell it before the moving trucks showed up). That included several foreign countries. In my family's experience, that included England, Iran, Ireland & Saudi Arabia. During the 80s, his industry stopped relocating engineers. This correspond…

We had someone buy our home for basically top dollar at the time about 20 years ago. They worked for Ford and Ford was relocating him to the area, and he bought the house. I was told there was some relocation expenses they paid, but I don't think Ford bought the house. Well, I know they didn't directly, because we sold to him - that's what the paperwork said. I think he got moving expense reimbursement, but that may have been it. But I know they sold it a couple years later as the market tanked, and must have taken a loss. I wonder if Ford covered some of the loss for him? (Bought at $295k, sold for $205k 2 years later).

Re: Nearly 40% of software engineers will only work remotely

#273

It's seldom a single variable decision. What percentage would say "remote only" if it paid 80% less? 50% less? 20% less? Etc. Some would take it but most would not.

It also depends where you live. I moved to the Midwest and while finding Bay Area salaries remote is difficult, finding remote jobs that pay +30% more than any jobs in this city is easy

Re: Nearly 40% of software engineers will only work remotely

#274

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

Leaving family, friends, community and the place you know is higher on my list of disruptive than selling a house.

"A lot of the lay-offs were senior technical staff like C++ senior engineers; seems more like a realignment to shift those jobs to cheaper subsidiaries like India, Pakistan, Mexico"

Re: Nearly 40% of software engineers will only work remotely

#275

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

We also have to be more specific. What does "going to the office" mean? Does it mean I'm going to an actual office, where I have my equipment all set up how I like it and a tailored environment that helps me stay focused and productive? Or is a bullshit open floor with terrible lighting and everyone is sick all the time because you're sitting face to face for 10 hours with someone you don't even talk to?

"The office" is a tool. It's like we've forgotten the reason for doing things. Software development is really not all that social. It's not akin as a factory or an orchestra or any of these other analogies that get tossed around.

Re: Nearly 40% of software engineers will only work remotely

#276

Earlier quoted context omitted.

The consistent response I have gotten from managers is that more or less - people fake work sitting in their homes or work multiple jobs, and we collaborate better when we are sitting in an office. They use this as a force function to pull employees back into the office. I call BS on all of these. Employees faking work - your hiring problem. Employees working multiple jobs - again your problem, keep them occupied wit…

> people fake work sitting in their homes People fake work sitting in offices. If someone is going to fake work in the office, why not let them fake work from home and safe everyone a hassle. Or maybe incentivize real work over fake work. I worked with someone in the office next to mine for a few years and he was running a side business the whole time. It was bizarre how brazen he was, but people are interesting and…

I keep saying - if they aren't doing the job you'd fire them even if they were in office. If you think they are working two jobs but they are getting their job done you have to ask yourself - are you paying for someone to get the job done (which in this scenario they are) or someone you force to sit in a seat for x amount of time each week?

Re: Nearly 40% of software engineers will only work remotely

#277

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

It can depend... there's a few colocation/shared offices in the Phoenix area. I know of a couple in Chandler, Mesa and Peoria in particular. Though I have a gigabit connection at home that's pretty stable and have my workspace setup how I like it.

Personally, I prefer an office space as I find the comradery is better. Being able to have lunch or general conversation is much more natural. Also, a commute that isn't too long (20-30m) is nice for ramping up on the way in and clearing the mind on the way home.

All of that said, since going remote, I don't plan to go back. I really want to move to a more rural location that better aligns with what I want in lifestyle/community. Of course, internet connectivity becomes crucial, and the current interest rates prohibit that.

I also don't think TFA is quite right on that being younger is the stronger reason for a higher chance of layoff. I think a lot of it comes down to experience and value provided from more experienced devs. It can definitely cut both ways and I have seen it in practice. I would suggest it's about perceived and actual value as well as a bit of office politics and agreeableness in the workplace that is more desired.

I do think that the nicest thing about more remote work, is it is more regionally competitive. At the higher end of the talent pool, one is able to compete for jobs that are much better paying that would be available locally, while still being less expense for businesses rooted in tech hub cities. This comes at the cost of communications, which you mention, though I think it's more than a 15% degredation in some cases. My prior position it seemed to hold things up for days on communications at times, with an international team.

Re: Nearly 40% of software engineers will only work remotely

#278
post #229

Earlier quoted context omitted.

I’ve never met a good programmer who didn’t always have a trail of unsolicited job offers following them. Obviously there are many situations, but I think many people can be selective about where they work.

And what does that mean for the largest group in the bell curve: the medium skilled programmer, who does ok but nonmagical work? Not everyone has the ability to be one or two standard deviations above the median.

Trust me they are being pursued by recruiters too

Because recruiters can't tell the difference.

Re: Nearly 40% of software engineers will only work remotely

#279
post #235

I could be convinced to commute to a satellite office that's not affected by rush hour traffic. There's a lot of real estate available in the burbs. These don't really exist though, and their expense far outweighs their benefits. The problem is that companies expect employees to be mobile when they are not. It's called putting down roots for a reason. Pulling kids out of school, buying a new house is very disruptive.…

I work for a non profit. After two years or letting everyone at home, this month they're forcing people to come to office at least twice a week. Not only that, anyone going to work has to book a desk in advance, otherwise they'll be sitting on the floor with their computer on their laps. This makes no difference to me personally, as I am a thousand miles away in another state, so I lucked out. I am still working from…

> leads to office politics

That's exactly what they miss. Those people became powerful by playing that game of office politics and now have nowhere to do that anymore.

Re: Nearly 40% of software engineers will only work remotely

#280
A huge swath of midrange companies will have a major competitive advantage, in my opinion, because they choose to opt-in to remote.

There might be one or two companies in the world I’d choose to move to work at. Even then, it’s a hard choice to make.

As long as remote is an option, that’s where I will work, even if I prefer another job on all other dimensions.

Post reply on HN