4 ms·
Cave and Commons is the way to go, as several other posters pointed out. I'd like to add the critical factor: team size. Once team size gets too large (say ove
by DanielBMarkham 18y ago
Cave and Commons is the way to go, as several other posters pointed out.
I'd like to add the critical factor: team size. Once team size gets too large (say over 8-10 people) random noise and distractions take over. I've seen teams of 30 try to do collocated, collaborative work environments and it just falls apart. At that size, the best I've seen so far is cubes, "study hall" and private rooms. That is, cubes for \half the day, a group "study hall" type atmosphere for the other half, and easily available small group work rooms. By "study hall", I don't mean a bunch of people being quiet, just a bunch of people in the same area working on group/individual tasks.
There's an interesting phenomenon that goes on in collaborative work spaces. Many times programmers get lots of benefits from working together but still would rather be left alone. So many times the team requires time that it works together, say for a couple of hours every morning, like it or not. Not everybody likes it so much. Many times there's a gap between "the way I like working" and "the way that I work that is the most productive"
Just goes to show that programming is not a technical exercise, as much as we like to talk functional code, security, and all the other bits and bytes bullshit. It's a human activity, and full of the irrational and quirky nuances that comes from working with hominids.