Why do programmers need private offices with doors?
blobstreaming.org
blobstreaming.org
"Remember back to high school math class. Now imagine 8 hours of high school math class back-to-back-to-back. Now add in "pop-quizes" (e.g. production issues) sometimes multiple times a day."
I think that once someone can relate to what day-to-day software engineering is like, they can empathize with why "walls" and "doors" are nice.
Almost nothing gets done.
Well, stuff gets done like helping folks out with their work by looking over their shoulder and helping walk them through things they are stuck on.
Our leadership is okay with this. They want us to have the face to face in-person time. And I will admit, it does help build relationships with those who do not excel at building relationships through a chat client.
My most productive programming hours are 11pm to 8am. I'll pull an all-nighter maybe once or twice a month and I get a stupendous amount of work done. That's the only time I feel a sense of complete solitude and focus. No Slack messages, no phone notifications, no noise from my neighbors, not a single disruption whatsoever for hours on end. And knowing I have a horizon that stretches on for so many hours somehow allows me to relax and tackle the most difficult tasks.
Repeating my comment from https://news.ycombinator.com/item?id=38693398 when this came up last month, DeMarco and Lister described flow state in their 1987 book "Peopleware: Productive projects and teams".
Here's the relevant text from the later 2nd edition: https://archive.org/details/peoplewareproduc00dema_0/page/62 ("Brain Time vs. Body Time").
571 other comments in last month's discussion at https://news.ycombinator.com/item?id=38691468
But really it does seem useful to have a door. Bad news might be rare, but unless you want to have the conference room imply bad news, you also have to schedule good news meeting in the conference room. Now all the meetings are in the conference room. Managers’ whole job is to go to meetings as far as I can tell, so we might as well give them the conference room I guess, haha.
For me personally, over a period of about 6 weeks, I needed a private room for a sensitive conversations on at least 3 days in each of those weeks. 2 of the weeks were for all 5 days.
3-4 of the conversation were related to employee's health so probably more than a typical period. But the period didn't cover any of the usual high sensitivity events, like appraisals or comp, so it's a bit of a wash.
Now that doesn't mean that I need exclusive access to an office (and I don't) but it is frequent enough that it makes an important part of my job very hard without easy access.
But that all obviously depends on details as to how many people you manage, org's views on management responsibility etc.
I advocate for most employees having offices, but we can still acknowledge that the reasons you probably want your managers to have them are very different than the reasons for engineers.
I think it would require a bit of “opsec” type thinking on the part of managers, maybe? If you always take meetings in your office, it is pretty easy to close the door discreetly.
If you book a conference room for one-on-one meetings, you have to do all your one-on-one meetings in the conference room. Otherwise, obviously, booking the conference room implies negative feedback. And if someone wants to do an impromptu talk that goes in a confidential direction, there’s some impedance added… none of this is to say it is impossible or unworkable, but it seems easier to just give everyone a door.
Also I think the focus on private conversations is a bit of a red herring. I can assure you, none of the engineers or sysadmins that reported to me wanted me in the middle of the cubes, constantly on the phone or having a conversation.
To be clear I think most employees should have offices.
I've tried to explain to them why I need to work without interruptions, much the same as the author of this has described, but they've never given it a thought.
I cringe every time the phone rings because generally the 1st thing they ask is "are you busy" and I always answer "yes, I'm working" and they blow right by that to tell me why I need to do something for them right away.
Gotta love `em.
I would hope there's significant amount of neurological research predating paulg's 2009 essay. Does anyone know? Is this just a version of "don't interrupt someone in the state of flow"? Csikszentmihalyi spent decades researching that.
my sweet summer children, private offices for every programmer was a thing at least as far back as around 1980, and at that time we didn't think "oh, we've just identified the need for this."
I was myself already noticing that I also liked working in a "bullpen" (big room, terminals all plugged into shared computer) and swapping jokes, syntax tips, and the like with my neighbors. Actually, when I read about people on here today talking about cli stuff, I think "it only seems a mess to you because you don't have more experienced folks sitting next to you in the bullpen"
Do you never have zoom or phone meetings?
If such tradeoffs are offered by different companies, there is no reason why they should not be also offered as by one company.
I'm certainly not interested in paying/taking a pay cut to generate more value for my employer.
Well you are breaking your employment contract by not giving “best effort”.
If your management finds out, they should fire you.
Anecdotally, neither I nor my friends have seen this happen. Putting in more effort just leads to an increased workload along with a "Meets Expectations" during annual reviews. I have a great manager now but their hands are tied as far as bonuses, promotions, and raises go. It's a bad sign when the best benefit I get is that my workload isn't cranked up because I complete tasks more efficiently.
I'm still young, but I doubt that I'll see anything similar to a bonus or significant pay raise due to performance in my career. I still put in my best effort, but I don't see any reason to take a pay hit to get better working conditions if I'm not going to get rewarded later down the line like you assume will happen.
Lots of discussion a month ago: https://news.ycombinator.com/item?id=38691468
That 5% of the time I have to really think hard on something? I do.