Open Source, Open Plan?

One of the best articles I've ever read on software development, was by Joel Spolsky - 12 steps to better code. To write really good software and delivery one time, you need to be scoring above 10 on this test - The Joel Test Do you use source control? Can you make a build in one step? Do you make daily builds? Do you have a bug database? Do you fix bugs before writing new code? Do you have an up-to-date schedule? Do you have a spec? Do programmers have quiet working conditions? Do you use the best tools money can buy? Do you have testers? Do new candidates write code during their interview? Do you do hallway usability testing? Out of all of these points, one stands head and shoulders above the others in terms of importance to me - 'Do programmers have quiet working conditions?'. In all of the companies I have worked at where software was being developed, the programming team had totally quiet working conditions, except my last company. At Simon and Schuster, the programming area was open plan, and next to the tea area, but everyone had respect for the staff, and kept the noise down. At Endsleigh Insurance, the programming room was very quiet, with a couple of cubicles at one end for the managers,but they didn't sit around laughing like hyenas - they kept quiet. At Palmer Environmental, if you walked into the development room and started yakking to someone at high volume, you got some pretty bad looks. You were expected to use one of the other meeting rooms for any serious discussions, and keeps jokes and banter to the kitchen area. But, at my previous company, noise was actively encouraged. My manager used to shout orders across the room, staff from other departments used to wander in and have a good old laugh with anyone they liked, and talk about rugby and cricket was expected every ten minutes. The 'analysts' sat in the same room, and were constantly on the phone, and was the help desk guy. It was like the proverbial bull pen. Getting work done efficiently was like trying to carry a tray of drinks while being pelted with eggs! If you are in charge of a software department, I implore you - give your team some quiet . The difference in performance will be huge. Every time a programmer is disturbed by loud noises, phone calls or inane questions, it takes them a good few minutes to recover their train of thought and get back into the 'zone'. The 'zone' is where good programmers will want to spend all of their time. Good programmers love to write code, and are just not interested in discussions about sport (lets face it, obsession with sport is a substitute for a personality anyway), or anything else that doesn't relate to programming. Give a programmer your insight into a cool new string handling function, or a rad Data access layer, and they will love you for it. Tell them that some fat sphincter just won the welsh open darts tournament, and they will call you a tool to everyone. Sadly, some managers think its great to spend time shouting, and stamping about while people are trying to concentrate.