News for hackers. Stuff that matters.
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.