408 comments

[ 2.9 ms ] story [ 315 ms ] thread
I hope they win, open offices are the stupidest thing since cubicles.
And yet I would personally prefer cubicles to an open office plan. At least cubicles provide visual interruptions, reduce the overall noise, and provide a space for you to personalize.
Cubicles may be better than open space but offices are still much better
I totally agree. Every argument I've heard against cubicles were actually arguments against poor lighting and lack of windows -- a well lit, green, many-windowed office that had cubicles would be much more preferable to open office plans.
Investing in everything but the people who work there.
I don't think that was the intent.

My guess is that this was planned in an era (sadly now) where open space is portrayed as the "cool" way to work.

Pretty much, the open space hype seems to have peaked in like 2010-2012, now we live in an enlightened time where even corporate leaders (gasp) are willing to admit different things work for different people.
I'm sure Jony Ive has an office.
Yes. Once I see all the big shots sitting elbow by elbow at a long table the whole day I will revise my opinion about open offices.
Musk and Zuckerberg "sit" among the peasants. It makes for a good photo op but in reality they have to spend very little time at their desk. At that level, they probably spend most of their time in meetings, and even when not, it's not like anyone would chastise them for behaving inconsiderately to other people in the office, or taking over a conference room as their impromptu office.
Same with Jack from Twitter. At that point it's just an empty gesture.
Open offices are a direct manifestation of Satan's plan.
(comment deleted)
It all seems so backwards. Instead of having collaborative working spaces with private rooms for meetings, doesn't it make more sense to have private rooms for working and collaborative meeting spaces?
I suspect the thought process is something like, "Collaboration makes the office more productive. Therefore, if we force the employees to collaborate all the time, we can maximize productivity!"
My company moved engineering into the same open office as sales and customer support, we can collaborate with everyone all the time!

Definitely a negative to productivity on my individual work because it's so much noisier in here.

Yes, they put our desks right next to finance, with that one person who is our "laugh really loud, laugh at everything and I mean _everything_" person.
We should make an audio output for our build scripts to play a really loud woodchipper sound. "Sorry, can't be helped, part of the process, the machine has to grind the source code up into small bits to fit into the CPU."
At least that way you can hear the sales staff selling features that have not been developed yet.
Collaboration is essentially contention, like CPU threads racing for the same memory location, needing synchronization. Synchronization kills parallelism.
The most productive days I've ever had at my current employer -- by a significant margin --- were when most of the company was not present (off-site or holiday). Being able to come in those days and work in a distraction-free environment was amazing.

Open office floor plans are the worst.

RIP July 5th when no one came into the office. I'll miss you till next year.
I suspect it's much simpler than that. Open floor plans give less square footage per person so you get more people per building. It's just cheaper to build open floor plans.
The "it's cheaper" argument for open-plan offices only really works when the company hasn't spent $5bn+ on the building. They could probably have quadrupled the floor space for the same price.
They'd have to sacrifice their avant garde spaceship design, though.
(comment deleted)
This is enabled by the fact that, despite how hard we try, we don't actually know how to track productivity, say nothing about changes in it that can be traced back to organizational decisions, or have anything approaching a model of productivity so that we might start to have predictive capability for how decisions impact it. So lacking a real metric that means anything, we cling to the ones that don't and as long as the lines move in the right direction nobody cares.
We've known, at least since the 80s, the aproximate amount of space people need to work effectively. Chapter 9 of Peopleware [1] talks specifically about this:

An excerpt:

>Before drawing the plans for its new Santa Teresa facility, IBM violated all industry standards by carefully studying the work habits of those who would occupy the space. The study was designed by the architect Gerald McCue with the assistance of IBM area managers. Researchers observed the work processes in action in current workspaces and in mock-ups of proposed workspaces. They watched programmers, engineers, quality control workers, and managers go about their normal activities. From their studies, they concluded that a minimum accommodation for the mix of people slated to occupy the new space would be the following:

- 100 square feet of dedicated space per worker

- 30 square feet of work surface per person

- noise protection in the form of enclosed offices or six-foot high partitions (they ended up with about half of all professional personnel in enclosed one- and two-person offices)

[1] https://en.wikipedia.org/wiki/Peopleware:_Productive_Project...

You and I both know that no MBA with delusions of grandeur is going to pay attention to Peopleware.
The WSJ story has some pictures of what it looks like [1]. There seems to be offices with doors, but they look like it seats about 20 people. There are also common areas with long tables between them.

https://si.wsj.net/public/resources/images/BN-UF776_0817CO_1...

https://si.wsj.net/public/resources/images/BN-UF775_0817CO_1...

https://si.wsj.net/public/resources/images/BN-UF777_0817CO_1...

[1] https://www.wsj.com/articles/how-jony-ive-masterminded-apple...

I don't get the complaints, that looks very cozy even if you have to share with what looks like a total of 4 engineers per room which is a reasonable number for collaboration. The second picture makes it look greater than 4, however.

Assuming the cubicles are walled off, it'll just feel like a college library meeting room.

Ok, just at a glance:

1. No separators -- you see everyone, everyone sees you. All the time.

2. No separators between neighboring desks, thus every flinch your colleague next to you makes distracts you.

3. No shelves and drawers. Where do you put all your papers, books?

4. At least based on the pictures, reflections of light, coming from every single angle.

5. The tables are way too small. There is just no space for multiple monitors to be put at a reasonable distance, which fucks up the eyes really fast.

What a joke. Now I love my large private cube even more, lol.
I basically had to put up with that every day in the college library. I don't mind glass offices until I get the itch to pick my nose. I get that the optimal environment for programming work is at home or in a private office, but they did what they could at what appears to be an economical compromise. I agree with the desk space, there doesn't appear to be any room for an external monitor at all.
The thing about the college library is everyone knows that you're supposed to be quiet there. Open offices, I find, are much more akin to the dormitory cafeteria than the library.

I hate that if I want quiet I can't have my monitors, keyboard, or mouse. And if I want those I'm sitting directly next to the loud and noisy office cafeteria between my very loud teammates.

This is _after_ I asked for a quiet location and they told me "it doesn't matter cause you never sit at your desk anyways" even though everytime they move me I find _one_ quiet spot and sit in it until the next move. But even if I sit there _every day for months_, apparently "I don't sit at my desk".

Combine that with a "no WFH" policy, commuter trains that have been declared to be in a "state of emergency" by our Governor Cuomo, and a no reimbursement for headphones policy and it's no shocker our retention rate is absolutely abysmal.

I just do not understand who thought to themselves "well, we're gonna have to hire a bunch of very talented people who need to abstract extremelt complex data flows day after day, so I suggest we put them in the middle of a _fucking zoo_".

I find myself constantly exhausted by days end as my brain copes with constantly trying to churn out work while being inundated by constant distractions and blasting music.

How about the people who come up behind you and shake your chair while you're in the middle of things to get your attention when you _don't even know they're behind you????_

Or the people who see someone with their headphones on and just walk up and start chatting away, because why could what I was focusing on be important, it's just a quick question, what's it matter if I get jarred out of my workflow?

Open offices are an absolute fucking travesty. I will never work in one again after this job.

Compare that to when I work from home, I get more done, I don't feel bad about resting for twenty minutes and coming back refreshed, my ears don't hurt, I'm not exhausted.

What a shit show.

Edit: I very rarely swear in my hacker news posts, but the amount of stress and misery and grief these layouts gives me, some one who just absolutely loves engineering complex software solutions... it kills me.

Remember being in college, up late night, working on some project, and you look up and four hours had gone by without you noticing? Remember that flow? That rapture? That concentration?

Now ask all your open office colleagues how many of them ritually experience that same solace, that same unbelievable connection with the work and problem you're solving. Why in gods name would you hire people who could experience that and rip it all away from them? Why would you make it impossible to get there?

Pick your nose and pick it boldy. Catch someone watching you pick your nose? Just pull out a booger and start examining it. Make them feel uncomfortable for staring at you doing a perfectly normal thing.
Surely they will put monitors or machines in there, so there will be separators.

I have worked in a similar situation, you DID get used to it quite quickly.

6. One person gets sick and sneezes, everyone gets sick.
Cozy? Looks more like a morgue to me.
(comment deleted)
Oh boy, two desks facing each other with low walls.

Here's what that's like:

You're looking at your monitor and in your peripheral vision, just above your monitor, is someone looking at their monitor. You're basically looking at each other.

They answer their mobile with their head phones on.

"Hey"

It looks like they're looking at you and you never saw their subtle click on the inline toggle below your view.

"What's up?"

Person on mobile points to their earbud to indicate they're not talking to you.

Later the same person gets an email that pisses them off and exclaims, "Are you fucking kidding me?"

It looks like they're scowling at you.

"Huh?"

"Nothing, sorry."

All day. Everyday. Fun times!

Let's not forget the constant awkward fleeting moments of eye contact with someone you barely know and don't wish to talk to.
the quick semi-smile meant to acknowledge the other person without starting a conversation that just makes things more awkward...
Why do you "barely know" the person across from you?? What, no team building budget?
Haha. In my particular case I was at the boundary of two departments. To make things worse, turnover was high.

Hmm, I wonder why?

Looks like an Apple store. Bet it's going to be as noisy as one.
The WSJ story says the offices are soundproof:

>A section of workspace in the circular, Norman Foster–designed building is finally move-in-ready: sliding-glass doors on the soundproof offices, a giant European white oak collaboration table, adjustable-height desks, and floors with aluminum-covered hinged panels, hiding cables and wires, and brushed-steel grating for air diffusion.

>The first prototype was ready in the summer of 2010, with pictures of trees on either end of the central area to evoke the landscaping and proximity to the outdoors. Jobs himself set the precise dimensions of the openings from one end of the central area to the other. The team quickly discovered that early versions of the small offices on each side of the central area were noisy—sound bounced off the flat wood walls. Foster’s architects suggested perforating the walls with millions of tiny holes and lining them with an absorbent material. In the completed section of workspace, Ive snaps his fingers to demonstrate the warm sound it creates.

That would be nice if people had private offices but it looks like a dozen or so to each enclosed area.

Sounds like (pun intended) that they've made it more like a concert hall. Instead of white noise with all the reflections you get to hear everyone in your jail block, er, work area nice and clearly.

I personally find that hearing a clear conversation beside me to be a bigger distraction as I tend to "lock on" to it instead of thinking of the problem at hand. So your damned either way, loud but more noise like or quieter but more distracting.

WOW, Holy Shit! Nothing about that office space looks remotely warm or inviting. Was this really the plan for that new campus all along???

Where are the white boards to write notes on?

I guarantee in a matter of months engineers will cover all those clear glass walls with posters and other things to block out all the obnoxious sunlight that will be coming in to blind them on their screens.

Other nit-picks, will Apple no longer all engineers the option to pick their own chairs? Those in the photos look like generic shitty conference room chairs and not ones I'd want to spend all day on.

Also, are those not sit/stand desks?

Those desks on the renders don't look like standing desks, but rather height adjustable desks.

Here in Australia all new offices are equipping standing desks for OH&S laws and workspace regulation compliances.

These are actually way nicer than I expected. I've seen much more distracting open office layouts.
Depends what you mean by "make sense". If you mean save money on office space per square ft, probably not. If you mean fit into Jony Ive's elite design sensibility, also probably not.
from the story ... "Prominent Apple podcaster and blogger John Gruber passed along rumors that some high-level Apple staffers are unsatisfied with the company’s open floor plan — which has many company engineers working at long tables with co-workers, instead of in cubicles or offices."

wow, "long tables" for lots of devs to work at, what can go wrong right? and i thought Microsoft open space had its issues, this sounds much worse.

When do people focus again?

Bench seating, work tables and open cubicles.

Apple? Famous for not letting their developers talk to people outside the project?

Oh, upper management is even more paranoid than that. It's what made this such a strange move for the company.
Does it maybe work like the Pentagon, where you can't just randomly enter any area?
I have heard that open office plans are justified by decreased cost. Does it make sense that they would build a 5 billion dollar office with open floor plans? I suppose given that large price tag there would be motivation to cut costs that way other than the fact that the open office plan as a fad still exists.
Maybe the justification is density, not cost. The floor space of the spaceship was finalized years ago and maybe Apple is trying to shoehorn more employees into that space.
Surely, they'll all realize that it takes courage to embrace the office layout of the future?

Jokes aside, this was a problem five years in the making, and as far as I can tell there was no secrecy about the plan. I'm surprised the complaints are only coming now.

You see ... all that precious space inside the building ... we just can't have private offices if we want to move forward and make great things happen.
And it's such a privilege to participate in the dialog between architecture and society.

(MIT dean of architecture on why inflicting a Frank Gehry building on CSAIL was worthwhile.)

It seems a lot of managers live in that phantasy world where people do nothing but collaborate. Do they really think that code gets written that way?
they heard about git once I guess…
That's what the managers have decided...while sitting in their closed-door office meetings.
Managers mark their value by how many meetings they attend. If their calendar is booked all the time (even with pointless meetings) it's because they are valuable.

Developers mark their value by what they create. Unfortunately people tend to think everyone is like them. In this example, managers tend to think since their value is through constant collaboration, they think everyone is valued in the same metric.

Man, I remember in college when we would be working long hours in the library on a computer lined up in a row of computers. Every one would be intensely working on what they needed to. Sometimes two would work together. This was especially true before presentations when we were trying to put our stuff together. It was neat. It was collaborative. It was fun. And we were happy.

Open floor plan is reminiscent of those days, but it isn't working. And I cannot figure out why. What's missing? Intensity? Work? Stress? Team building therapy? Or just trust? Whatever it is I hope we figure it out.

IMHO, I think what's missing is focus. In college, people in the library were there to get stuff done and would leave when they were done or needed a break. In today's workspace it's less likely that everyone is completely focused on doing work every hour of the 8 to 5 work day, and that's what creates distractions.
You nailed it.

In the company's mind, everyone in the office is there to focus on exactly the task at hand all the time. In reality, it comes in spurts and each person has those at different times. When people are in there unfocused, they just distract the people who are focused.

In library you are not supposed to make noise. Go outside to have a chat. Proably that helped.
For one thing, I'm guessing you didn't do all your work there, only specific things for short time periods. If you worked in that environment all day every day, the fun would wear off eventually. Also, as people relax, they'll get noisier.
The default being quiet, and respect for others doing focused work and trying your best to not distract them, was certainly a key ingredient.
Probably the fact that in a library, there is a cultural expectation of quiet, built over the years by librarians shushing loud people. Thus, if you want a quiet place to work, you go to a library. I need a librarian in my (open) office.
Perhaps it's the expectation of near silence (you might work together but you'll keep your voice down) and lack of visual noise in the library?

In my open plan office I have:

- People walking past my desk

- People walking behind me

- People walking in front of me, over the "wall"

- A team that regularly has stand up meetings behind me

- Coworkers that talk loudly at their own desks, near mine

- Coworkers that talk loudly in a small more private area, ~10ft away

- A small meeting room with a door that doesn't isolate noise very well

- A kitchen ~20ft away with a loud espresso machine

Plus, I'm in a large room and can hear conversations up to 50ft away. Given the number of people, there's nearly always one happening.

In a library, you've got a quiet space with an expectation that people will keep their voices down. Study desks often have high walls in the front and to the sides, to block out visual noise. They're also often isolated from major traffic areas.

Libraries are designed to optimize intellectual work and study, open plan offices are absolutely not.

The comments about library etiquette are on to something.

But I think it also helps that most of the other people in the library are probably strangers, and if a couple of them are talking it's probably about something quite different from what you're working on.

"Team" conversations that might possibly be relevant to your stuff are the worst distractions.

Agreed - I liken it to my college experience: if you want to eat or drink anything other than water, or talk to other people, you go to the coffee shop.

If you want to focus on your work and take breaks to do the rest you go to the library.

I always chose the coffee shop, so open offices don't bother me hugely. The caveat is that a good pair of headphones is a must.

> ... other people in the library are probably strangers

This is the key thing--our brains process familiar and unknown voices differently. Recognition of a familiar entity and the ensuing reactions are automatic, and they all have a processing cost.

In college, nobody was likely to walk up and interrupt you.

In the workplace, they are, unless you have an office with a door you can close.

Hopefully, more and more companies experience backlash from this. It is a horrific mistake to add distracting elements to most programmers environments. Even worse, in my open office plan, they put our very loud finance group right next to us. Absolutely no thought of noise management was considered, except for putting in horrible "white noise" generators that set off my tinnitus Thankfully, my direct manager is understanding and let me turn off the one directly over my head. And by directly over my head, I mean about 4 feet.
Fuck, that sounds awful.

It's hard for me to believe that there are techies who haven't ever heard of Peopleware, have never heard of Joel Spolsky and his FogBugz offices, and have never consulted even a single authority on what makes software developers productive. It's even harder to believe that those people are responsible for diverting giant sums of money towards making palatial office buildings that will house thousands of such developers.

The problem with the Spolsky example is that Atlassian with their huge open-plan offices completely overshadowed Fog Creek in just a few short years.
In some ways. They did raise $60 million, too, which didn't hurt. I think we're doing just fine having a successful business on our own terms.

For what it's worth, Atlassian's NYC headquarters is… our Fog Creek offices, complete with private offices for coders. More about that here: https://medium.com/make-better-software/apple-is-about-to-do...

(Source: I'm the CEO of Fog Creek.)

The NYC 'headqarters' is not even on their list of locations

https://www.atlassian.com/company/careers

so I'd be surprised if it hosts a signficant percentage of their development workforce. As far as I know their Sydney office is really the heart of their operation and it's very open plan.

I don't think that's a problem, more a question of leadership's priorities.
Economic success is not a proxy for doing things properly. Many dysfunctional companies are very successful otherwise.
I worked for a company that did the noise generator thing. For a long time I couldn't figure out where my headaches were coming from and chalked it up to job-related stress.

Then, I got to travel to a QUIET remote office with only 10 workers and no noise generators for a high-stress, deadline-critical project. The headaches disappeared immediately. When I got back to my normal, headache-inducing office, I clocked the baseline noise level at 50-60 dB.

Any company that thinks those things are a valid solution to noise issues is very, very wrong.

This is only a rumour, I would wait for some photos to appear to confirm this.

Anyone got any recent images now people have started moving in?

The reaction from the troops is a rumour. The fact that almost everyone has to work in open space is not. It's well documented fact.
I was under the impression that when John Gruber quotes a 'rumour', it's because someone at Apple has personally given him complete, direct, but off-the-record information. He seems very well-connected.
Apple has the money to afford whatever it wants. If it's like any other place I've seen, I expect there's longstanding communication of one or another sort from high performers that they want distraction-free environments.

From what I've observed of such high performers, they are not anti-social nor anti-collaborative, nor are they "crippled" in either respect. Rather, many of them are the most capable in these areas, because they actually pay attention and focus on getting things done -- and done as well as time and resources allow.

The fact that Apple, like many workplaces I've observed, chooses to ignore this and push a paradigm that increases their stress and decreases their effectiveness and efficiency?

Well, as I learned in my own experience, over the years: This is just a fundamental level of dis-respect.

I don't know anything about Apple work internals, specifically; the last time I intersected with those peripherally was in the early '90's.

But when you blatantly disregard what employees tell you -- and in this case, "professional" employees who have a high degree of training and awareness about the tooling they need, including their work environments, to be most effective. Well, that's just disrespect.

And employers who persistently engage in such, deserve what they get. I hope -- because at some point, this counter-productive... "ideology" needs to die.

P.S. Those employees that want cubicles or open-space? Fine, give it to them. I don't want to dictate environment, either way.

Trust your employees to select what works best for them.

And measure the results. Objectively, not in the typical performance review ex post facto rationalization and justification.

In my own experience, top performers cautiously (politics) leapt at the chance to work from home and otherwise gain undistracted blocks of time to adequately focus on complex problems and program management.

Those who embraced the cycle of endless meetings, interruptions -- including environmental -- and superficially-addressed delegation? They faced the same problems, month after month, cycle after cycle.

I am fairly close to someone who works at Apple. His team is avoiding the new spaceship building. He mentioned wanting to keep his office, but that was just one part of several different complaints, including just "it turns out that the building isn't big enough for most of the people who work at the HQ in Cupertino," and "My team would probably have to split up in awkward ways because not everyone would be able to work in the spaceship (due to space constraints)."
The building looks gigantic but most of it is empty space due to the donut shape. I wonder if they plan to ever build in the middle.
Open offices diminish workers to cattle status. Most work, even the kind many developers would not think of as being so, in tech companies requires thoughtfulness often and collaboration less often. I consider open office plans to be disrespectful and an indicator of second-class status.
I also see them as a lack of respect.
Another point of view would be that by having 'senior management' in the same rooms, at the same desks in an open office, they are more human and there's less of a perceived barrier between them and everyone else - which could be seen as a positive.
Managers often end up commandeering a meeting room to get around not technically having an office.
Sure, and I wouldn't want meetings taking place at desks anyway as that would be disruptive, but having the CEO at a 'normal' desk like everyone else, and having them there for any time they are doing tasks alone, I think humanises them more.
I've actually seen that reasoning also used in support of these plans. My experience is that these senior leaders rarely occupy their desks. Instead they have permanently reserved meeting rooms or even private offices in addition to their reserved open area desks.
The "I don't like open spaces, so therefore my team doesn't" is the same failure as "I don't like an office, so my team doesn't get offices".

Developers are humans, and not all humans have the same preference. I personally prefer to work in an enclosed space that includes all my team. Open spaces suck for me. A closed office with just me in it also sucks, for me. If anyone on my team is more productive in an office, I'll do my best to get them an office.

There are two fundamental problems that always show up on this issue:

1. Believing that "I am human. My preference is X. Therefore X is the preference of all humans", and

2. "Office as a signal of seniority".

If a team can get past both of those, they should be good.

OT, but is there a good book on the history of offices, at least in American workplaces? What existed before cubicles?
Private offices for managers and more senior types, desk farms for the hoi polloi, and a separate, deafeningly loud typing pool. Very much like today's open plan, but with individual desks with some separation rather than long benches.
Don't have a good book but a quick search led me to this Wired post: https://www.wired.com/2009/03/pl-design-5/

Anecdotally, when I think back to images from the early century, I'm led to believe that open plan with higher level employees in private offices is actually the historical norm. While the actual nature of work of course has changed, I'm not so sure that everyone having their own private office has ever been a reality other than a select few employers.

I might be in the minority but I HATE cubicle farms and love open office design. Just give every a sound cancellation headphone if they complain. To me cubical farms are depressing.
There are many of us who code in spurts, and spend the rest of the time goofing off on Reddit or hacker news. At the same time, we'd prefer not to get judged on what percentage of time we have Facebook open on our monitors, and more on the work we do. But when everyone can see what you're doing, it's hard to get rid of the nagging feeling that you're being watched.
That's why working from home is the holy grail :D
It's not really goofing off, I absolutely work in several focused spurts during the day. Which is also why I'm never that fussed about turning up on time because I never do any real work in the morning anyway.

Can't dig it out now but John Cleese did a good talk on creativity explaining why this works and how brains solve problems in the background which is why inspiration hits in the shower and on the train. By alternating between focusing then procrastinating and ignoring work you can force a decent cadence of creativity into your work.

The thing is sound cancelling headphones tend to cancel out noise, not conversation. So they actually make things worse for those of us who need to think occasionally.
For me, its not just about the sound. I can easily lose focus by being visually over-stimulated too, and there's no way to fix that except for cubicles.
> Just give every a sound cancellation headphone if they complain.

God dammit.

> Just give every a sound cancellation headphone if they complain. To me cubical farms are depressing.

Just give everyone some anti-depressants if they complain?

Just give "them a good whack" if they complain. FTFY
IMO, it is all in the execution. Open offices can be terrible, but they also can be good, just like private offices.

There's a huge difference between a few dozen desks in a bare concrete hall without any dividers between desks or a few dozen desks in a room with sound-dampening dividers between desks and lots of sound proofing on the walls and ceilings.

I work in an open office, and barely hear it when people three meters away make a phone call.

they screwed up my award winning office design. common section down the middle with individual offices on opposite walls, large enough for pair programming, one end of the alcove has windows above shelves, other end has multimedia. offices to be used as small conference rooms and manager offices, without windows, are in a perpendicular central hallway. i designed this over 10 years ago and a virtually identical design was used for my company's buildout the following year. no one is assigned to the common central table. offices can have the door open or closed depending on the occupant need/desire to be heads down or passively participate with others. each alcove houses a functional team
I recently watched the movie Office Space.

Oh, such a wonderful working environment. To have the privacy and isolation from distractions and interruptions that a cubicle gives. What I wouldn't give to work in such a great office space.

It's funny that the work environment became worse than Mike Judge imagined it would be in Office Space. Wait till that happens to Idiocracy!
Working in open office plans is simply awful.

Personally I believe remote work, for any tech-enabled employer, makes the most sense. The impact on infrastructure by removing commuting alone could maybe help save the planet. And our collective sanity.

Wouldn't it be nice to have ISPs that can provide an infrastructure that could actually support that? I think so.

The hideous effects of cluster-fucking hundreds of thousands of people daily just needs to stop. Tech companies are guilty. They're huge and, humbly opined, are idiots for making it worse and not really needing to. Top that off with an open floor destination and.. damn, work is beat.

(comment deleted)
Nah, it's fine. If it gets noisy, put on headphones or go sit in a different place for a few hours. Individual offices can be awful and isolating. Cubes can be an acceptable compromise but it still kills a lot of spontaneous conversations.

You gain a lot with open space plans: more interaction with coworkers, cultural gel and socializing. And of course, the company can cram more people in the same place.

Well you can put a team in one room, and a kitchen to cater for several teams - like design studios actually. IMO that's the best balance, but maybe that's a bit luxurious, cattle pen-wise.
I strongly feel the best option (if remote work is not a possibility) is individual offices with team designated collaborative work areas. This allows people to quasi self organize, with the default option being that they have their own space.
(comment deleted)
You are contradicting yourself. More interaction leads to more noise and now you are advising people to put headphones on or leave the place entirely. How are you supposed to culturally gel and socialize under such conditions?
And for those that find headphones distracting and for which there isn't a viable "somewhere else?" Such casual dismissal.
"Nah, it's fine."

Yeah, I don't see the problem either.

In fact, I don't understand why companies don't just install long airplane style seating rows in their open office plans and have everyone work from laptops literally on their laps... that way we'd be able to cram even more people in the same space, and just think about all the useful socializing and spontaneous conversations that would occur as co-workers were climbing over each other to head for the restrooms.

/s (just in case)

Just use mothballed planes as offices. A steward could come down the isle every couple hours and give us snacks and drinks. When the build breaks, they can turn off the air as punishment.

Hook them into some sort of huge ferris wheel, saves on space and keeps attrition low.

And have a mandatory seat belt rules, and disallow restroom 45 min after work begin and 45 before end of work time.
> If it gets noisy, put on headphones

Headphones only go so far. If you don't have good headphones (or, gasp can't afford good headphones, or don't have the time or money to shop around for good headphones), then you end up with a band-aid that doesn't really work because... well noise bleed is real. You either still hear what's happening around you or the people around you can hear your music. So they talk louder, because they need to make sure they're heard by whoever they're talking to. They don't stop the distraction of someone walking by. They don't stop someone from trying to start a whimsical conversation just because they walked by you.

Sadly, I'm still looking for headphones that can be comfortably worn over my ears + glasses for more than an hour at a time. In-ear ones have other comfort issues.
I have a set of Razer Krakens that are pretty comfortable even if I wear them all day, and I wear glasses.
I expect this will depend a lot on your frames - if the arms on your glasses are thick it'll be more inclined to squish into your head.

That said I'm really happy with my Logitech G930s - I usually use them wired to keep the charge (the usb cord length is _very_ generous) but they're just fine wireless too, and do a good job staying put if I'm moving around a bit.

My only complaint is that they seem to be sensitive to 2.4ghz interference, which can kick them off the wireless connection. Since there's no wired override (plugging in is purely for battery) this means plugging in can't save you. Once I switched my devices at home to prefer 5ghz wifi, it went from 5-10 times an hour at its worst to once or twice a month (and I can maybe blame that on the neighbours).

Look up the Sennheiser Bluetooth ones.
Yep, I also have this problem. The only (wired) headphones that are big enough to fully circumvent your ears and thus comfortably sit for an hour or more, is the Sennheiser HD 558. Unfortunately, it's wired.

There doesn't seem to be a bluetooth alternative. The newer Sennheiser models like the 4.50 are not as big as the HD 558. There's a dongle-based wireless headphone, the Logitech G533 which is big enough. It's meant more for gaming, and looks like it. It may only work on Windows, though.

That's some fine sarcasm you've got there. That said, there are apparently people defending this opinion.
Are you sure your parent post is sarcasm? The sad reality of the modern tech industry is that I actually think that is a serious response, though I wouldn't be surprised either way.
I wouldn't be so quick to think of it as sarcasm.

"Ask IT for headphones" and "find a quiet spot in one of the lounges" are almost direct quotes from the CEO of the company I work for. In the few years I've been working here I have seen the CEO at his reserved seat in our open office area once, and the CFO twice. Not one other C-suite have I seen at their reserved seat in the open office area to do work.

"Keep collaborating you peasants."
As someone who has never worked from a private office or classical cubicle I tend to agree, but maybe I just haven’t had a chance to experience the productivity explosion that comes with those options.

I think open office is fine so long as the density is not too high. Ive seen conditions where you are shoulder to shoulder with your co-workers, which seems awful.

I have always had around ~8 square meters of space in my open office layouts. I value being able to casually converse with my nearby colleagues.

IMO it depends on the job. Open floor plans are good for ops roles and some front end roles where teams of people are engaged in substantially similar work driven, especially event driven work.

Lower density low cubes are ok. Offices are great for managers, PMs or professionals like attorneys, engineers or accountants.

From my perspective, remote works if the culture is friendly to remote or conditions like traffic make commuting a misery for everyone. As a manager of managers, we historically have had a lot of problems with remote employees compared with people in the office.

(comment deleted)
I don't want to gel or socialize with my colleagues. I want to work with them. If we become friends, we can socialize outside of work.

I'm not paid to chitchat or stand around eating birthday cake. I don't need to love people to work with them. For the most part, even as a systems architect, I don't even need to talk to them. A few emails, echats, and meetings are sufficient.

This may sound harsh, when I heard they were pulling down the cube walls, I threatened to walk. I got to keep my high walled cube, but everyone else was surprised one Monday with low walls. A week later, after the whole office rioted, everyone got their walls back.

If you need/want company, go sit in a common area. But don't take away my isolation. And tell those kids to get the fuck off my lawn.

> A few emails, echats, and meetings are sufficient.

As a sysadmin, I overhear a ton of stuff that people don't put into chats. I like being in the office and being able to hear what people are talking about in the workplace; it helps me do my job better.

So I'm supposed to pack up my computer, a couple of monitors, my notebooks and stationary and move it all whenever the noise levels are distracting me from focussing?

Sounds efficient.

> but it still kills a lot of spontaneous conversations.

Yes, I think that's the point.

If it gets noisy, put more noise into your ears?

> more interaction with coworkers, cultural gel and socializing.

Yeah, I like wasting time as much as anyone else. It's still bad.

Good work interactions either happen better in offices, or are meetings.

I'm a Solutions Engineer and whenever I have to get on a sales call or demo at my desk it's a disaster - it's simply far too loud and too much background noise is heard on the call.

This is just one more complaint in a long-list that I have with this arrangement. Makes me miss my cube!

Can you use a conference room?
I work remotely too and I often think about how much this has reduced my environmental footprint. It would be interesting to see some figures on how much of a positive impact it has.
I mostly work from my home, which is self-sufficient for water (rain tanks) and heating (firewood), produces its own electricity (solar), has its own septic, produces some of our fruit and veggies and all of our eggs, with virtually no food waste that is not fed to the animals and low amount of landfill waste (you really think about it when you take it to the tip yourself). I occasionally commute to the local coffee shop by bicycle, or drive to the beach, and work digital-nomad style on mobile internet.

Then I jump on a plane to my employer's office every few weeks.

I wonder how that stacks up?

I worry about how much it increases my environmental footprint. I have an entire house of climate control being used for the sake of one person. I have lights in the house being used for one person. Sure I don’t commute by car, but I’m willing to bet commercial HVAC systems are more efficient per person and commercial lighting systems are more efficient per person and all of the other things that go into an office are more efficient per person when they’re being shared by 100+ other people.

I haven’t done any math on it, but it’s something I do worry about.

Turn off your central and get a window unit and a desk fan for your home office. I don't run central most of the time because it's expensive.

You could always cool of the way God intended, sweat your ass off. :)

This depends on a number of factors, including where you live and how long your commute is.

In California electricity is increasingly generated by renewables (~25% in 2016) with the goal of hitting 50% by 2030, which looks achievable. We actually have a surplus of renewables during the late afternoon that can cause power prices to go negative. Between this and conservation measures like insulation the impact of home energy use does not look that high. It's also getting better over time.

The big problem in California is transportation, which is still petroleum-based autos. You don't commute by car but many people do. Knocking that out is one of the best things you can do to combat global warming. For example my commute, which is about 50 miles generates between 60 and 80 pounds of C02 daily assuming 3-4 gallons. That's assuming a fuel-efficient car. (Fortunately I only do it a couple of days a week.) At some point the car will be electric but mass replacement of the fleet is still a long way off.

[1] https://en.wikipedia.org/wiki/Energy_in_California

It sounds like most of what you're worried about could be mitigated pretty simply.

Use a smaller heater, solar panels, LED globes etc.

Environmental arguments are silly when living near the office will likely use public transport and remote workers are usually out in the countryside so will likely use 2 cars extensively compared to a city worker using public transport 100% of the time.
I totally see the issue with open offices, especially if they're densely populated. But I think home office has certain shortcomings as well: Communication quality is not as good over video or text chat as IRL, nuances are missed more easily and sharing a whiteboard is harder. In addition, I have the impression that some people slack off much more because they feel "unwatched".
(comment deleted)
If employees are measured correctly, it is impossible to slack off. In engineering, measuring hours is silly, measuring output and throughput is what determines performance.
And what do you propose is the correct way of collecting these measurements?
Results. Delivery of requested work products on schedule with quality.
> Results. Delivery of requested work products on schedule with quality.

Because we all know that software estimation is a solved problem. Particularly with non-technical managers.

>Because we all know that software estimation is a solved problem. Particularly with non-technical managers.

Oh wonderful. They don't do estimates at your company then?

This was explained to me by one of my professors 20 years ago. There are two types of company mentalities:

A: The high school mentality. You show up 8 to 5 but it doesn't really matter what gets done.

B: The college mentality. You pass or fail based on how well you do on the test. Show up if you want, or don't.

The way I see it, if your manager can't tell if you are productive, he or she has no business being a manager and they are the problem.

  Oh wonderful. They don't do estimates at your company
  then?
You can do estimates without thinking they're accurate enough to let you detect high- and low-performing employees.

Intern Ian's tasks are simple and well documented - so they always have good estimates. Veteran Victor is great at complex, poorly understood bugs - but he often takes longer than estimated to fix them, as often the cause is hard to find.

It would be a foolish manager that would punish Victor for performing worse than Ian.

If you actually had solved this problem you'd be a trillionaire, alas.
LOC /s
You measure your output in lines per second?! It's clear you are more productive than me then.
/s is the way to say you're being sarcastic on Reddit. So they probably meant that lines of code measurements are popular, while they shouldn't be.

It's difficult keeping up with the internet lingo.

For what it's worth:

* You can simply see on Slack if the person is set to Away. In that case they're busy, so don't bother asking them any questions in a traditional open office plan.

* A better open office plan has a quiet room where people can collaborate in quiet. You can just send someone a message, asking them if you can ask them a question when they have time. You take your laptops with you into the quiet room. Then you keep the quiet in the office itself.

* A good manager knows what people are up to, and how they do it. It's part of their job. They also talk to employees face to face, individually, so they have better understandings on matters. If your manager is not a good manager, then no fancy metrics will help.

* Remote working is fine, and especially in the tech industry I find that there are more people willing to work remotely. I am fine with people wanting to work remotely, and everyone is abroad at times, or needs some time alone for deep focus. I do like to see everyone come together regularly, even just working together in quiet builds up a bond, and periodic informal tea & coffee on the work floor makes people a lot more open in approaching me and trying to test ideas together.

I do understand that commutes can be problematic for people in certain areas, and that some people really like peace and quiet during work hours. During job interviews, people try to see if you are a good fit for where you are going to be working (I can't speak for everyone of course), but it never hurts to ask if you can meet the team before signing a contract, if for some strange reason you weren't introduced already.

at a risk of dropping below the HN value threshold:

whoosh

I got it and appreciate the mutation of my statement.
(comment deleted)
(comment deleted)
I mean you know who is good in your team don't you? It doesn't have to be on a spreadsheet, qualitative results still count.
I generally agree but without some set of metrics/principles to measure against it can become a contest of favorites easily.
>it can become a contest of favorites easily.

I'm afraid that is unavoidable. Any metric you track can and will be gamed before the first collection period.

I think by defining a set of metrics and company principles that employees can measure themselves against. Furthermore, by taking into account peer evaluations which reflect on how valuable you are to your team.

An example might help demonstrate my thoughts: Last year I worked on a new UI for customers and went through 7 failed experiments. Does this mean that I suck at my job or that our designer dreamed up a failed interface or the business never should have started this initiate? The designer designed what the business gave a green light to, I wrote the code to put this in front of customers. Are we all failures or is one of us a failure? My opinion (at least in this situation) is none of us failed.

Why? Because the business justified the project based on a need customer's were showing from data they collected and evaluation of the market. The designer created something that after a handful of iterations was green lit for an engineer to build. I was measured in terms of how difficult iterations were. For example, did it take an entire re-write to go from experiment x to x+1 or did you as an engineer anticipate some possible future directions that project could go which made iterations more easy to integrate into existing code.

Some of this is subjective, some is objective, but your peers (team, stakeholders, and adjacent teams) all have an ability to measure and provide feedback to you.

Different jobs require different types of assessments but I focused directly on software engineering since I have best frame of reference.

I work most efficiently when I don't have the stress of having the amount of work I'm doing measured. In my experience the more trust given by the employer that employees are working, the better and greater the output.
I know I'm weird, but I don't recall ever in my career wanting to use a whiteboard
I hear they are great for asking how merge sort works during interviews for a CRUD application.
I've used one precisely once in my career to date and that was only to make modifications to something someone else had already done on there.

There's a huge one to the right of me which hasn't changed once in the 6 weeks I've been here - although since it says "NEXT SPRINT: [project X]" and Project X still hasn't really started, I guess it's always correct...

I do use it from time to time, especially when trying to get a common understanding about a fairly complex problem with other devs.
If I make 90K a year salary for a company and contribute significantly to projects that bring in > 1,000,000 and increase efficiency and deploy times to hours instead of days as one of my functions then the days I slack are paid for.

IMO a much better model than 'sit in this cube and make noises while I (manager) am looking at you'. That is the reason IT is broken + interminable process improvements like agile culture.

I've been in multiple openoffice and cube environments and I sort of laugh. I can do more in 25 minutes than most 5 year experienced people all day (without google and copypasta). I don't need your corporate propaganda and hustle. I have my own and mine is productive and gives me a life and nice things + actual enjoyment of the process and product.

> I don't need your corporate propaganda and hustle.

- I've never worked in a company with 100+ people so far - All the teams I've been in were fairly small (6 people or less), with flat hierarchies and little formality

No, it’s not simple.

I am awfully bored of these “everything is simple, open offices are uniformly awful, everybody should be remote” arguments. Yes - this works for some people, in some workplaces. In other cases, it doesn’t work. I’m fine with my open office space, and I prefer working from an office - which is a bike ride away and better equipped than I am.

How about instead we accept that there are almost certainly trade-offs involved in these areas, and that maybe building an office space that works for everyone is important? Provide open office space for those who thrive in that environment. Make sure there are private areas for those who don’t. Establish a culture that supports remote workers, and encourages good behaviour in shared areas. That, if anything, is simpler.

It's sort of telling how far out of my way you went to form an argument against something you manifested all by yourself.

You're a bike ride away from the office that you prefer? Fantastic job of deflection.

It's rather obvious that there are trade-offs, isn't it? It's pretty clear to me, at any rate, and there's nothing inherently wrong with providing an office. Shame on your words coming out of my mouth.

In relation to the expense of providing "office space" for several hundred the cost of a fat pipe is pretty darn cheap, were that it existed.

If you don't have the need to live where you work there are "simple" choices any given person can make that will make their lives easier, happier and, hopefully, more fruitful for both themselves and their employers.

And besides, having worked in offices (real ones), cubicles (and half-ones), bullpens and open spaces (including fields) I feel I am more than qualified to provide my own opinion on the matter without implying that my "simple" opinion is somehow not compatible with your own.

Open spaces suck to work in. It's that simple.

For you. I have a really long commute, and I can work from home if I'd like. I still prefer coming in to my open-plan office. I think his point was that it's not this simple for everyone, even if it is for you.
You are allowed to have your opinion on what it's like to work in various kinds of offices. I absolutely, 100% accept that people have different working styles, and one of those styles is those who prefer to work in a more isolated fashion.

But, like I said, I'm annoyed that it's become obvious accepted wisdom that "open offices universally suck" – because it's emphatically not that simple. I respect your need to work in a different environment, and explicitly advocated ensuring that you are able to do that – so please respect my preferences as well.

Sure, sure. I only rejected the implication that I was somehow ignorant of the factors involved and just la lala painting with a broad brush of simplicity and righteousness that was somehow at odds with your perceptions. Apart from that I'm pretty much in agreement with your opinion. The reality, for most, is that remote is still the black sheep of options and that only if it's an option. I have zero against an open office plan if those that provide them embrace all the options. I am fortunate enough to have exactly this situation. I have a haul into the (open plan) office, which I love (the haul), mostly because I have three pedals and fast roads but the burning of a few of the days hours to get there and back is more wasteful than not. Far too many are put into the position of long commutes and, omfg, astronomical costs of living to get just a teensy bit closer. I think my only real point, apart from providing just another opinion, was that if capable employers embrace these options in totality then the human condition could be a bit better off for it - open plans or not.

These are just opinions, right? Right. We both have valid ones that are actually pretty closely aligned. We seem to both appreciate our fortunate circumstances which are, for the most part, at opposite ends of the "we're fortunate" spectrum. I regret having inadvertently annoyed you, but, in all respects, you shouldn't be annoyed with anyone's opinions simply because they seem to not be like your own. I think we're good here. Are we good here?

> Provide open office space for those who thrive in that environment. Make sure there are private areas for those who don’t. Establish a culture that supports remote workers, and encourages good behaviour in shared areas.

Yep. This is what needs to be done. One thing I'll note is that in my experience, remote workers are 2nd class citizens unless the company is a remote-first company. And if the company is bought or gets new management, the remote workers are the first to go.

In my experience, non-managers are all 2nd class citizens. Given the option to remote full time for 5 years at company A vs. be in the office full time at company B and be a 1st class, 2nd class citizen, I'll chose A.
I think if a company offered an open office plan with the option to remote full time, you might be the only person in the office. :)
I own/run a co-working space which is almost entirely open plan. Many people here elect to work in this sort of environment rather than at home. People use headphones if they need to focus.

Personally, at home I am too easily distracted - I can pick through the fridge or cupboards, or read news sites forever. At the office, my screen is visible and as such I'm more likely to stay focused. I vastly prefer the incidental social interactions in an open plan office too.

Not everyone loves open-plan, but if it was truly a disaster, the space wouldn't be full.

Out of curiosity, what percent of them are developers?
3-5 are programming. Others are architects, marketers, etc.

In a previous iteration of the same space, there would've been anything up to 75% programmers but the bulk of them bought and moved to another open-plan office.

isn't a factor that the "open office" subscription costs typically an order of magnitude less than the private office?

(thinking of wework)

And when you've built this office and nobody chooses to work in the open office?
Then you haven't done your homework by talking to your people and should be ashamed that you have designed it like that.
If you are a developer who has to check in code, then you need a quiet place for focused work. You can try to argue that some developers don't need that, but those who can achieve peak concentration while context switching and talking to others are biological curiosities, if they exist at all. I haven't met anyone like that.

Now most employees working in tech companies are not developers. There is a whole "developer abstraction layer" (https://www.joelonsoftware.com/2006/04/11/the-development-ab...) but tech companies should at least have a place for all of their engineers to do quiet, focused work that is free of distraction.

I would also say that many people who are managers and do marketing also need a quiet place for focused work. So do QA people, infrastructure engineers, etc.

A larger point is that there are so many easy ways to communicate and collaborate now that to fix the physical plant to optimize for communication is just plain nuts. Why not use something that is very expensive to change, like the architecture, to meet needs that can't be met with software. Software can let you talk to someone easily, but it can't give you a quiet space. Only the architecture can do that. So I would err on the side of giving everyone an office with a door and then creating some common meeting spaces for them rather than building the office to have open offices and then adding a few multi-use closed door areas.

Hypothetical scenario here:

Lets say that you have a 5 minute question, that would save you an hour of work.

In a closed/cubicle style office, you may be less willing to bug your expert co-worker. In an open office, it may be perfectly normal to turn to your left, and quickly ask you question.

Sure, you are taking time out of your co-worker's day, but even so, on the net whole, asking the question is probably a net benefit time saver to the company.

In closed-style offices, it is a big gesture to walk into someone's office and ask a question. I'd feel less comfortable doing that.

Even sending a slack message still feels less comfortable than just turning your head and asking a quick question.

Coding is a collaborative process to many people. I don't want to schedule a freaking meeting for my simple question, or walk into someone's office. I'd probably just not ask if I felt like I was bothering someone.

That five minute question may well save you an hour of work, but it's just as likely - I'd say_more_ likely - to steal an hour of productivity from the person you ask.

Just send them a message in slack. Don't be so obnoxious as to assume that whatever's bugging you at this moment is automatically more important than whatever your co-worker is on.

I don't know why it feels weirder to slack them then it does to turn your head and ask. One demands immediate attention, the other allows them to answer when they have bandwidth for it. It seems obvious enough to me which is more polite.

Agreed. I think teams need the discipline to _not_ just turn around and start talking, but to message on Slack/etc. However, once that has been done, having the person right next to you can make the process of answering the question much quicker and easier when they are ready.
But there is the whole glass castle principle you forgot to me too. That 5 minute break does not take 0 minutes to recover from in some cases. You need to rebuild your glass castle in your head over and over again. So in reality it might take just as much time to go back to full productivity.
Reducing interruptions from people is a feature; not a bug. Maybe you would only do it when it would save you an hour; more commonly, people have a much lower "interrupt someone trying to work" threshold.
Interrupting other people to ask your question doesn't mean that you are engaging in collaborative coding. Collaborative coding in the sense you describe, doesn't really exist. What does exist is multiple people working on the same project, with their code communicating via interfaces, etc. Each person needs quiet focused time to do that.

The other issue you raised is that sure, your productivity may go up if you interrupt someone and get a question. It's clear that we don't want to optimize for that, because the interruption may cause someone else a loss of 30 minutes before they get back into the zone. It's not just 5 minutes. And 20 minutes into that recovery of concentration, someone else will interrupt them and ask another question. And they will also interrupt you. That creates a very frustrating experience. So it's better to ask your question asynchronously. You will get your answer when the person takes a break and relaxes their concentration. Both of you will be able to exercise control over when you can concentrate on getting your work done. Having that sense of control and ability to concentrate is critical to being productive.

Civilized people use email or whatever is the asynchronous communication medium du jour
I've wasted entire days answering a few five minute questions and not being able to get anything done. IF you have a question, email me and I'll look at it when I can and maybe arrange a time to talk about it. Being randomly interrupted because it will save an hour of your time means I'll never get any work done at all (and get none of the credit for your work).
save it up and ask them at lunchtime
The main problem is that everyone around you hears the question and the answer. This can create more discussions but it probably disturbs a lot. Especially when you place different teams in the same open space. Suddenly you are disturbed by all kinds of discussions that has very little to do with _your_ job.

I basically think it disturbs more with questions in an open space than when you go over to a cubicle/room.

That's the theory of why open plan is good.

In practice it doesn't pan out that way, because most 5 minute questions don't save that much time (answer was a 2 minute search away), don't take that much time (take much longer), and overall cost much more time (due to loss of flow).

Most (if not all) programmers need a state of flow to write quality code. Achieving flow after an interruption can easily take 15 minutes or more. If the environment discourages a state of flow by having frequent brief interruptions, the quality of the code written in that environment will be poor. If you had the ability to collect the right metrics, you'd probably find that bugs disproportionately are written right after an interruption.

those who can achieve peak concentration while context switching and talking to others are biological curiosities, if they exist at all

You've just described everyone who has ever programmed against the clock in a hollywood movie.

How would pair programming work? Wouldn't that contribute to a noisy environment as the two developers talk to each other?

I don't like large open plan offices, but I think a small room just for my team (6 devs) would be helpful.

(comment deleted)
> If you are a developer who has to check in code, then you need a quiet place for focused work

Don't talk on behalf of me.

Maybe because I'm relatively younger and I've mainly worked in open-plan offices, but I have zero problems with them. I'm not so easily distracted that simply having someone else's presence is enough to throw me off. When I need to buckle down and get some 'serious developing' going on, I just put on some headphones and listen to The Social Network soundtrack. I am more productive by having my colleges around me so I can easily pair-program or pair-design.

The point still remains: everyone is different and what works for one person won't work for everyone (I for one could never work remotely for any serious period of time). Again, we need to make sure we're building office spaces that can adopt to these different people and the ways they work.

> When I need to buckle down and get some 'serious developing' going on, I just put on some headphones

More proof that a noisy "collaborative" environment is not conducive to work that requires deep concentration.

>When I need to buckle down and get some 'serious developing' going on, I just put on some headphones

by "serious developing", I'm guessing you mean "actually programming".

There are at least two gears:

1. Code you have worked on before and can extend and maintain in your sleep.

2. Deep spaghetti WTF code that someone else wrote 5 years ago, makes no sense, the code IS the documentation, and you need to extend.

#2 might require some silence.

If you're working for a much-desired company rather than building crusty wordpressers then that "home 10 min bike away from the office" is going to cost you more than half your salary
The trade-off is the medium-sized office: a room containing up to six people who are all part of the same team.

You get all the advantages of being able to talk to people, and none of the disadvantages of conversations drifting over from the rest of the office. And there's more of a chance that if your immediate co-workers are discussing something then it's actually relevant to you.

Noooo! You still get the chatter and it's harder to ignore if it's familiar people talking about semi-relevant stuff.

Also, it cements the idea that things are done by teams, not individuals.

Things are done by teams. They are also done by individuals within those teams, but any given feature is likely to have quite a few fingerprints on it.
That's a good middle-ground in my experience, if a larger hybrid office space isn't possible.
Yes, this can work well. You still have to be careful and not mix people that has to do a lot of phonecalls or loud discussions in the same room as developers.
Apple has a lot of experience with people working in offices. You'd think this experience would inform the "pod" design. But they also do high fidelity prototypes, at least for product.

Further down thread, someone quoted the WSJ article:

The WSJ article said Apple prototyped one work area, and then multiplied it across the available space. "Hav­ing set­tled on an over­all shape, the team then broke it down into smaller parts. “One of the ad­van­tages of this ring is the rep­e­ti­tion of a num­ber of seg-ments,” says Ive. “We could put enor­mous care and at­ten­tion to de­tail into what is es­sen­tially a slice that is then re­peated. So there’s tremen­dous prag­ma­tism in the build­ing.” The ring would be made up of pods—units of work­space—built around a cen­tral area, like a spoke point­ing to­ward the cen­ter of the ring, and a row of cus­tomizable seat­ing within each site: 80 pods per floor, 320 in to­tal, but only one to pro­to­type and get right."

Prototyping one version seems un-Apple. I would have expected them to have prototyped many office layout options, had people work in them for six months each and rate them or otherwise measure quality.

I wouldn't be surprised if Apple's choice here is actually quite good, but perhaps I wouldn't be surprised by the opposite.

> remote work

It doesn't help if you're in the Bay. Home, road, sewer, curb, sidewalk construction, 3 neighbors with leaf blowers regimens nearly ever day...

And that's just this year.

(comment deleted)
Have a kid or know someone who does? Get that kid to do the work at all 3 houses. That way only noise one at a time and probably after school 3-5pm-ish
Open office plans are awful, but I hate remote work. It's nearly impossible for me to concentrate at home, and being able to get facetime with collaborators as and when it's needed is valuable.
Speaking as a designer who works close with devs. I think a lot of people championing remote work who are remote workers themselves don't seem to realise how frustrating it is working with them.

Fumbling around getting them on call every meeting, having to have them ramble on about something wasting peoples time if they misunderstand something because they're not in the room and we're all too polite to just tell them to shut up and move on, having to take special time out of my work to go on a 10 minute call that could be sorted in 20 seconds standing behind sometimes desks.

It's a very engineer-centric idea that they can just solve everything remote but if you're building a product that relies on design and more human focused work it can be an absolute nightmare having to work with a remote engineer.

Interrupting someone at their desk might take 20 seconds of your time, but it is easily a 10-minute interruption of their work.
I'm happy about German regulations. This would not fly for long in any company with a Betriebsrat ("work council" is apparently the English word) once noise levels get broken.
I'm sitting in an German open-office setup right now. There is nothing in the regulations to forbid these (and most of these Arbeitsschutzgesetze only are applicable to industrial settings).
I'll never understand the fascination with firms repeatedly going for the open office plan. I remember seeing pictures from the early 20th century where such offices existed full of people typing away. I don't know how they handled the noise or the fact they couldn't isolate themselves to do their work whether it was repetitive or novel in nature. It just seems like firms think of labor as a singular mechanical process and not as something that's done in an irregular and discoordinated fashion (as I've seen in my personal experience from working in factories and currently working in software development). I really think managerial practices need to update with the facts instead of forcing the facts to fit with their expectations.