Live data from Hacker News

Open Office Layout is Bad for Brain

infoq.com

11–20 of 67 posts

Re: Open Office Layout is Bad for Brain

#11

Earlier quoted context omitted.

I'm sure you have extensive research to support this conclusion - can you share it with us? Sometimes the most obvious opinions and beliefs turn out to be wrong, and it's useful to see the actual research. Thanks.

When categorizing information, it is possible to recognize personal opinions as such and handle it appropriately.

Link?

Re: Open Office Layout is Bad for Brain

#12
What if you had a cubicle layout, but each of the walls could be slid up or down. So it converts between open plan and concentration cubicle mode? Having the walls up implies you are deep in concentration so people shouldn't disturb you.

Though perhaps would just leave their walls up constantly

Re: Open Office Layout is Bad for Brain

#13
The problem is that the people who decide how to layout offices, don't do the kind of "stateful" work that requires long periods of concentration, and don't understand those that do. Their work is broken up into much more discrete chunks. PG talks about this in his essay http://www.paulgraham.com/makersschedule.html

Re: Open Office Layout is Bad for Brain

#14
Its all about change and shared state. Humans (unlike, say, chickens or purely functional systems) cache state in their heads about the world. In fact the brain operates so slowly compared to a processor that without caching we could not operate. For example, when we catch a ball the reason we are able to predict its trajectory is not because we measure its current speed and direction and then perform some calculation and repeat for every frame. It is because we compare it with the cached (and to some extent abstracted) memory of a thousand balls we caught before, find the closest match and do a little extrapolation from it. The book 'On Intelligence' covers this. The phrase he uses to describe the human brain is a "memory prediction machine" The problem with state of course is not the state itself, but the fact that there is more than one copy of it. In a purely functional program (or a chicken!) there is only one copy which is passed around, nothing is retained. If you put your hand over a chickens eyes they just go completely still, nothing in, nothing out. In more stateful systems the best we can do is to minimise the sharing of state i.e assign ownership of the state to certain subsystems. As humans are stateful this also works out to be the best model for them. This means that the optimum situation for quality in programming is to have one person develop all of the code. Its not always possible to do this and so the next best thing is to try to split the solution up into subsystems with well defined interfaces. Even at this we often have to assign a small team to each subsystem and we usually try to further decompose that but effectively at this point we are sharing state between people. Everybody needs to update their cache so that they all have a very similar mental model of the solution or there will be problems. They need to update their cache all the time as it is a model of a world that is being changed by the solution itself as the objective of the solution is to change the world in some way. The problem is that when the state of the world changes its not as simple as passing that state value to one of the actors i.e. Its not like passing some simple value like an integer around the place. The truth is that when the state of the problem changes in some signifigant way then the people involved need to have time, in peace and quiet, to update their complex model in a way that is consistent with the change. They have to figure out what the new information means in the context of the problem and more importantly they need to give their brain time to come up with a solution that fits with the new state of the problem. So there are two ways a system based on shared state between people can fail. 1) Somebody fails to get notified of a state change. 2) Somebody does not spend the time to properly integrate this into their understanding. In either case that person will go around with a faulty model of the system and that is when the bugs start to happen. As far as I can see the agile guys seem to be primarly focused on 1) and neglect 2). I think you need to work on both (given that you have no option but to work on a system with many people in which you cannot completely isolate the functionality to be implemented by each person). So what does this have to do with office space? Have an open plan office but tell people to stay at home for the morning, or tell people to stay at home every second day. i.e. Make sure they are communication AND make sure they have time on their own to digest the communication properly. The reason I know this works is that I worked like this as a contractor for a while and it was easily the most productive period I ever had. Much more productive that working in an open plan office all the time and even slightly more productive than working on something completely alone.

Re: Open Office Layout is Bad for Brain

#16

Its all about change and shared state. Humans (unlike, say, chickens or purely functional systems) cache state in their heads about the world. In fact the brain operates so slowly compared to a processor that without caching we could not operate. For example, when we catch a ball the reason we are able to predict its trajectory is not because we measure its current speed and direction and then perform some calculatio…

Use paragraphs.

Re: Open Office Layout is Bad for Brain

#17
None of the research has been about open programming environments. The article quotes two studies that did not study open programming environments, and the rest is opinion and speculation, albeit from some respected people.

So when they say "If you are just getting into some work and a phone goes off in the back ground it ruins what you are concentrating on" they are talking about a room full of people who answer phones as part of their business.

My most successful project was done in an "open" office, with the five programmers' desks arranged in a circle, facing out. We could all concentrate when required, but we could communicate immediately when there was a problem. Sometimes an interruption was annoying. Most of the time the communication paid of hugely. I think programmers are good at judging when to bug another programmer. That said, we had an awesome team.

In my experience, a bunch of programmers in offices is a great way to get lots of the wrong thing done. It may be because when I've been in this situation, the team was not as experiences as the team above. Or it may be that offices kill communication, discourage bouncing ideas around, and encourage "going dark".

When I hear of open offices that didn't work, there's usually more shit policy coming down from management and being imposed than just the open office.

That's the most important thing: What does the team want?

Re: Open Office Layout is Bad for Brain

#18

Its all about change and shared state. Humans (unlike, say, chickens or purely functional systems) cache state in their heads about the world. In fact the brain operates so slowly compared to a processor that without caching we could not operate. For example, when we catch a ball the reason we are able to predict its trajectory is not because we measure its current speed and direction and then perform some calculatio…

Use paragraphs.

may be he works in the open space office.

Re: Open Office Layout is Bad for Brain

#19

Its all about change and shared state. Humans (unlike, say, chickens or purely functional systems) cache state in their heads about the world. In fact the brain operates so slowly compared to a processor that without caching we could not operate. For example, when we catch a ball the reason we are able to predict its trajectory is not because we measure its current speed and direction and then perform some calculatio…

I believe this is what's generally called a "wall of text". The lack of paragraphs drastically reduces my willingness to read it.

Re: Open Office Layout is Bad for Brain

#20
post #3

Even with its problems, an open plan is preferable to small window-less offices or cubicles.

I'm sure you have extensive research to support this conclusion - can you share it with us? Sometimes the most obvious opinions and beliefs turn out to be wrong, and it's useful to see the actual research. Thanks.

[deleted]
Post reply on HN