Personally, I have no difficulty with noise (I prefer working in coffee shops to at home), and being able to easily start a design discussion with 4 or 5 engineers when necessary is extremely valuable. I totally get why some people don't like it though.
I'm fine with coffee shops over home (and did the same in college), but coffeeshop noise is "white noise" -- whirring espresso grinders, a blur of conversations between people I don't know about things that aren't going to activate my distraction monkey.
When I was at a large defense contractor the work was broken down into such small chunks that each engineer was essentially off on their own working on their piece of the system. In fact, that was the way all engineering, not just software engineering, was done there. There might be a point where two or three people would need to discuss an approach, but that wasn't the majority of the time.
The company I just finished at works multiple small contracts simultaneously. Because of the small scope it was very common to be the only person working on the code for a particular project, though there was more collaboration than at my previous company.
The place I am going seems to be more like what you describe, so it will be interesting to see if my opinions of open office layouts change after that.
That "easy conversation" is not scheduled, and now I need to stop what I am doing, listen to you for an hour, and still finish the rest of my tasking on time.
or, rephrased, the ability to destroy 3 man-hours of productivity on a whim.
I honestly do not understand this statement. Are you trying to say that if you were in cubes, you couldn't do that? You couldn't ask people to come over and talk something out? And are you stating that your design discussion is more important than whatever they're working on?
[1]: https://www.scientificamerican.com/article/ask-the-brains-ba...
Sometimes success depends on willingness to use ear coverings and stimulants (caffeine, ritalin, adderall), and willingness varies.
I'd rather pay for a wall than overload my body with drugs and a clamp on my head.
I'm going to guess that there's some individual variation in preference for quiet / noise. I'm the kind of person who can't really get deep work done, like writing proposals or novels, in noisy, busy environments. I look at all the people, listen to the sounds, and generally can't get into a state of flow.
That being said, I've met lots of writers who say they can't work in quiet rooms because they need some stimulation or they go nuts. Lev Grossman, for example, has talked about writing most of the Magicians trilogy (the first one is good! https://jakeseliger.com/2009/08/28/the-magicians-lev-grossma...) in coffee shops.
I suspect that on average most people would be better served by quiet focus, but that a fair number would not be.
If this is true—anyone doing industrial organization research may have a research topic here—I don't know how it would be implement organizationally, especially because offices and layouts are almost instantly going to be linked up with status and hierarchy issues, and most people will want the higher status option, regardless of whether it fits them well or not.
I got a pair of Etymotic In-Ear Headphones[0] which have kept me sane for several years now. They have interchangeable tips with a NRR on-par with foam plugs. Worth every penny in an open office.
[0]http://www.etymotic.com/consumer/headset-earphones/hf3.html
Also, I seem to be the minority in comments, but I don't mind people talking around me. I don't use my ears/hearing to code, so it doesn't distract me nearly as much as chat windows or anything visual on my laptop. I suppose the real issue is people having interesting conversations around me... But I have headphones and music if I need to concentrate (I probably only wear them for 1-2 hours a week to block out conversations).
Every week one a new article like this is posted, and every week the comments are overwhelmingly "open offices are bad". Every week I meet more people like me who don't comment because they don't feel strongly about protecting open offices, and would like the people who are upset by open offices to find their comfortable place.
There really are quite a few of us who don't mind open offices... I'd guess it's probably a majority of people... We don't really want to impose on others...
My only real concern is that the people who want their own offices tend to also have seniority and want natural light... I've seen these people carve out their own personal paradise, while blocking other's ability to have a good working environment.
Context: Mid-thirties, Sr Engineer in Seattle who has worked for small startups (< 10) up to Amazon.
My solution: Ability to concentrate is a teachable skill. Every skill-based sport has to teach players how to focus on the goal and ignore the distraction (hence my assertion that Golf isn't skill-based). We use enough sportsball analogies in coding, so I'll add another.... Coding in an office is like batting against a pitching machine.
My coding has very little to with sport-like activity and is more like the task of a lone clocksmith (although we have a team, individuals have quite large chunks of codebase carved for themselves).
For some problems I am straining on the edge of my working memory capacity.
The problem with the distraction avoidance is that it demands mental resources. If there is some benefit in training working in a stresfull environment there could be a sound proof room for such a purpose where employees could go for a limited time to train. The inverse of large open office/small quiet room pattern.
At first level there could be just white noise in the room. Once that is mastered as an added stimulus the feet could be placed in a bucket of icewater. At the next level the room is filled with monkeys. Etc.
My initial reaction is that there seems to be much bigger issues with the way your company is structured. The words you're using ("lone", "carved", "straining on the edge") suggest a stressful situation where each individual carries their own weight... If that's the case, I can certainly see why you'd be upset by someone else impeding your ability to work. I wouldn't last long in an environment like that, either pushing it to be more collaborative, or just leaving.
I can't imagine any coding that isn't improved by adding collaboration (a great starting point is code reviews... make PRs early and get opinions on rough-cuts). If you don't have this in your current environment, I highly encourage trying to kickstart it... you're really missing out on a great way to remove stress, improve quality, and have more fun.
The inherent technical complexity of the components is such that sometimes a feature needs days of coding - thus the 'more locksmith, less of a ballgame' analogue. I should have perhaps pulled some other analogue.
- Better/Faster communications. I can ask and answer questions on the spots vs. scheduling a meeting. This is gaming changing. For the same type of question, I can get answered within 10 mins vs more than 1 day. This is a HUGE productivity boost.
- Better team culture. Sitting next to each other make the team much closer. More likely to go to lunch/dinner, hang out, and become friends outside of work. This will give people empathy to each other and more willingly to help/unblock you.
For the noise issues, I get around it by blocking heads down time in my schedule and find a quiet corner in a office.
I dunno, I just don't feel particularly unproductive. I thought maybe I just didn't have any point of comparison, but then I had a few days working from home and it didn't seem massively different.
A lot of people here are talking about flow, but I don't really feel the need for concentration for the majority "tactical" level coding, and when I run into sufficiently complicated "strategic" level problems, I find it much more effective to discuss them than to try and solve them on my own.
Factories have huge machines, whih create added value. They have a good reason for loud noises and need for ear protection.
Offices, on the other hand, are places where people come to create added value by mostly by thinking (if they are programmers).
Are there people who enjoy the bustle of open office while trying to untangle a decade old piece of C++ spaghetti? Whose work output it actually improves?
I'm trying to figure out if the open offices are bad mostly for everyone or just for someone like me.