News for hackers. Stuff that matters.
Re:Commuting Kills by rayiner on Wednesday August 12, 2015 @06:24PM (#10051145)
The article argues for telecommuting to reduce commutes. I think a far less radical approach would be to open multiple offices and put teams in more affordable secondary cities. Modern technology has made it pretty easy to spread your organization across multiple offices. I work at an organization of less than 35 people that has offices in three cities. Outsourcing IT/HR/building administration makes it pretty low-cost to have additional offices, to the point where it might actually be cheaper when you weigh the fixed overhead of each location against the cheaper office space outside NYC/SF.

I live in Baltimore now, and before that in Wilmington, and I'm astonished that more companies don't have offices in those cities. Both cities have a lot less traffic than D.C. and Philadelphia, respectively, and are well-served by rail. I'd imagine there would be a lot of talented people who would sign up at offices in those cities so long as they weren't backoffice locations and they could still do frontline work.

Re:Commuting Kills by munificent on Wednesday August 12, 2015 @06:28PM (#10051173)
That works OK, but it increases the costs of reorganizing teams and projects. If your project structure changes frequently, it really helps if that just involves moving people from one room to another and not having to tell them to find a new home.
Re:Commuting Kills by rayiner on Wednesday August 12, 2015 @07:14PM (#10051381)
I guess that depends on what you think the value-add is of offices versus remote working.

In our organization, the value-add is forcing everyone to be on the same work schedule, promulgating organizational culture, giving managers an idea of peoples' workload so they can load-balance, and meeting the need of people to socialize. We cross-staff on a per-matter basis, and we'll generally conduct inter-team communication over email and phone whether even when the team is within a few doors of each other. Email is efficient and asynchronous. We get together in person at milestone events, where, e.g., the whole team will fly in and take over a conference room for a day or two to prepare for a big upcoming event.

If you think the value-add of offices is facilitating informal, day-to-day inter-team communication, than obviously having people in different offices makes reorganization harder. And admittedly, its been years since I was on a software team. That said, even at that time, I found people dropping by my cube, instead of emailing, to ask a question about an API I restructured to be annoying rather than productive. It's PIO instead of DMA--a waste of clock cycles.

YMMV.

Re:Commuting Kills by munificent on Wednesday August 12, 2015 @08:11PM (#10051577)
> I guess that depends on what you think the value-add is of offices versus remote working.

Right, which I think is a calculation people need to take seriously. There are real benefits and trade-offs on either side and articles arguing that one is uniformly better than the other always come across as terribly misguided to me.

The physical and social environment that a social animal like a human spends the majority of their waking day in has a profound impact on almost every aspect of their lives. We should be thoughtful about how we arrange it.

Re:Commuting Kills by lukeschlather on Wednesday August 12, 2015 @07:36PM (#10051470)
There's a definite benefit to colocation for software teams. When someone is poring over gigabytes of logs and stack traces there's no substitute for someone more experienced looking over their shoulder, maybe grabbing their keyboard and typing in a few commands of their own then handing the keyboard back and making a few suggestions.

There also is a definite benefit to letting less-skilled developers interrupt the more skilled. Skilled developers without interruption kind of become data silos. They're extremely productive, but they could have a multiplicative effect on others' productivity that is wasted.

Even if most interruptions are useless, it's still worth it for the times when a senior dev stops a junior dev from wasting a week puzzling over a stack trace or implementing something useless.

Re:Commuting Kills by stephengillie on Wednesday August 12, 2015 @06:48PM (#10051270)
The other way to do this is basically a 100% remote company that owns coworking offices, and only lets employees cowork from there.

To rephrase, think if WeWork closed their doors to non-WeWork employees, and let their employees work from any WeWork, or from home.

Re:Commuting Kills by 300bps on Wednesday August 12, 2015 @06:38PM (#10051219)
I've worked in Wilmington, Delaware and I'm surprised any company chooses to have an office there. I had coworkers robbed at gunpoint a block from our office in the financial district, strong arm robberies of cell phones, angry and violent homeless people everywhere, etc. Add to that a high city wage tax and I just don't get it. I worked there for eight years and it seemed to just get worse and worse.

Very apparent how bad it was when DuPont of all companies even moved out of the downtown area.

http://www.newsweek.com/2014/12/19/wilmington-delaware-murde...

Re:Commuting Kills by diogenescynic on Wednesday August 12, 2015 @07:19PM (#10051410)
I know this probably sounds crazy to folks from the Bay Area, but I would gladly move offices if my company had remote offices in Boise, Minneapolis, Milwaukee, Chicago, or Denver. I would even take a small pay-cut as long as I came out ahead when you adjust for cost of living. I don't know why no companies seem to offer this.
Re:Commuting Kills by lbaskin on Thursday August 13, 2015 @12:12AM (#10052222)
I feel the same way about NYC. I can see why early-stage companies want to be in the city, but all these Fortune 500 companies, big law firms, and banks wouldn't even have to move very far. Instead, I'm stuck on the subway every day for over an hour (each way) with a few thousand of my nearest and dearest.
Re:Commuting Kills by kctess5 on Wednesday August 12, 2015 @07:27PM (#10051437)
I'd imagine this doesn't sound crazy to many of those Bay Area folks. Making a large salary isn't nearly as much fun when you throw it all into rent/mortgage payments.

I've heard that Austin TX is a good city for CS people - high paying jobs, low(ish) cost of living.

Re:Commuting Kills by mmaunder on Wednesday August 12, 2015 @08:05PM (#10051556)
This is a brilliant point. If you look at Amazon and their radical expansion in the South Lake Union district (down-town Seattle) and the commuting capacity problems that creates - One wonders why they don't base satellite offices on the east side of Seattle (Redmond, Bellevue where Microsoft is) and give employees that option.

I think for large companies this is an excellent alternative and solves the problem where employees can't telecommute because of sensitive IP or security clearance.

Re:Commuting Kills by OrwellianChild on Wednesday August 12, 2015 @07:14PM (#10051379)
For startups and new business, assuming you can draw talent, I can see this approach working... You also hear about this happening in Google Fiber cities, etc. Relocating people is a lot harder than relocating/decentralizing place-of-work, and making people go "rural" or "suburban" might not sell well for folks who are already city dwellers (i.e. the majority of the talent pool).