News for hackers. Stuff that matters.
Re:Just shut up and let your devs concentrate, advises Joel ... by dredmorbius on Saturday October 08, 2016 @04:10AM (#12666127)
John Seeley Brown, in The Social Life of Information, has a pair of anecdotes from Xerox's repair staff and either Xerox or Kodak (I think) customer service.

The support techs used to have a morning coffee session before heading out into the field on their calls. These turned out to be hugely useful tech transfer opportunities as repairmen would share both their unsolvable problems (machines which had broken and couldn't be fixed) and "This One Weird Trick" solutions.

The second anecdote involved customer service operators, who had previously, if I'm remembering this correctly, shared floor space with techs, but had been moved to their own space. Following the move, there were two specific operators who were able to help out customers by not following the specific scripts they'd been provided, but rather by supplying actual useful questions, diagnostics, and suggestions. When studied by management, it it turned out that one was a veteran of the former seating arrangement. The other, however, was a more recent hire. She did, however, sit next to the more senior rep, and had picked up tips listening and talking to the other employee.

The lesson I'm drawing is that you don't need people to be interrupted all the time. But you do need them to have some opportunities for a free-wheeling exchange. Finding the right balance point between heads-down work (the Xerox techs, for example, were mostly on the road and at customer sites, so they wouldn't have had input from other techs), and exhange opportunities.

In academia, there's the teaching vs. studying/research balance. A few days of lecture and sessions, with other time devoted to actual research, gives that balance of peturbing your own thinking and exposure to new ideas, and focusing on your own work. E.O. Wilson addresses that in his recent book, Letters to a Young Scientist (along with advice to avoid as much teaching and administrative responsibilities as possible).

Re:Just shut up and let your devs concentrate, advises Joel ... by taneq on Saturday October 08, 2016 @04:46AM (#12666185)
A company I used to work for had expanded past its available office space, and so they had to rent another office nearby. They moved all the upper management, project managers, and engineers (basically the 'cool kids' / 'important people') over to the new office, leaving some admin staff behind at the main office with the workshop.

The resulting loss of communication between workshop and everyone else caused havoc and a bunch of things went wrong.

Re:Just shut up and let your devs concentrate, advises Joel ... by dredmorbius on Saturday October 08, 2016 @05:50AM (#12666333)
There's a well known international company who "rationalises" (or did a decade or so back) its office space by putting all contractors, regardless of assignment, on a single floor.

I found myself wedged between a contingent working COBOL and a very chatty (and pleasant) graphic designer, with the sole other contractor in my unit located at the extreme opposite side of the building, and my direct reports a half dozen floors up.

I suppose it made sense at some level....

Re:Just shut up and let your devs concentrate, advises Joel ... by keithpeter on Saturday October 08, 2016 @06:34AM (#12666436)
Classic example of resource allocation by org chart.
Re:Just shut up and let your devs concentrate, advises Joel ... by taneq on Saturday October 08, 2016 @07:36AM (#12666572)
That seems about as logical as putting desks in alphabetical order.
Re:Just shut up and let your devs concentrate, advises Joel ... by dredmorbius on Saturday October 08, 2016 @09:38AM (#12666896)
I plan on organising my future business by weight. With daily weigh-ins.
Re:Just shut up and let your devs concentrate, advises Joel ... by mamon on Saturday October 08, 2016 @07:25AM (#12666545)
Most offices already have dedicated space for discussions and exchange of ideas. It is called "kitchen", or "watelcooler area". Rest of the space should be private offices to do some quiet, focused work.
Re:Just shut up and let your devs concentrate, advises Joel ... by douche on Saturday October 08, 2016 @10:14AM (#12666992)
One of the things I miss about working in blue-collar jobs is the sanctity of the coffee break and the lunch hour. 9 o'clock, noon, 3 o'clock, tools down, everybody goes to the break room and has a cup of coffee, shoots the shit, catches up on what else is going on.

The plant I used to work in also did daily standups. They worked a hell of a lot better than any I have ever seen in software, since they started the minute after everybody was supposed to punch in, rather than some amorphous time mid-morning when somebody decided there might be a better-than-average chance of everybody finally dragging into the office or there not being some other regularly scheduled meeting.

Re:Just shut up and let your devs concentrate, advises Joel ... by dredmorbius on Saturday October 08, 2016 @11:04AM (#12667156)
There's a huge difference between work which you can do tools-down without a lot of fuss, versus work which involves keeping a ton of state in your head. I've done both myself, and there's a distinct difference between working with your hands and working with your mind entirely.

Not that tools-based work can't involve thinking. The design or planning elemments of carpentry or construction or machining or cabinetry can be quite cerebral. But there's that hand-eye tangibility that's missing.

Re:Just shut up and let your devs concentrate, advises Joel ... by clacke2 on Saturday October 08, 2016 @07:26AM (#12666547)