[dvtrn]

I think that valuing your uninterrupted time over the team and the product shipping is the truly selfish mindset.

I struggled mightily to find a tactful way of putting this to words, but this states it nicely.

My focus in responding to a teammate asking for help isn't on my time, or at least, it's less about my time and more about the objective behind what motivated a teammate to ask for help in the first place: shipping the feature/product.

If it helps clarify ambiguity or confusion for me to wheel over to this person and verbalize the solution they're looking for and work out the blocker with them by sitting right next to them for 5 minutes when they ask for my help, and we get the best possible outcome as a team, that's what I'm going to do.

Excellently said, snowman.

[z0r]

If you're a manager and you're getting compensated for keeping the wheels greased for your team, that's great. But if you're a regular IC being selfish about conserving your limited attention and energy isn't immoral at all. Being the guy who helps everyone else get stuff done often goes unrecognized in any meaningful way. Worse, being that guy all the time (rather than some budgeted proportion of your time) can prevent you from getting the stuff you will be recognized for shipping from shipping, and can cost you the focus needed to benefit in other ways (learning/practicing your deeper technical skills).

[dvtrn]

I'd like to reply to this in a similar manner as I did to another: it feels like there are extra variables being thrown into this that were never brought up from the start of this large discussion thread.

Being the guy who helps everyone else get stuff done often goes unrecognized in any meaningful way.

Valid, but irrelevant, I feel. I am a senior on my team, a junior asks for help. It might not be necessarily moral or even ethical to give them the time of day the second they ask for it, but it is a professional courtesy that I don't go looking to receive superlatives and accolades for.

If a contributor to the team has a question that affects their ability to contribute, that person should get the help they need. I happen to be sitting close enough to them that we can discuss the solution quietly enough so as not to be a distraction, and I do so.

What came from this were all sorts of wild extrapolations and suppositions that doing this created an otherworldly distraction to the rest of the workforce; and it is that mindset that I'm challenging. Not that people don't deserve a distraction free workspace, but to what ends we're willing to go to avoid that distraction while also operating in a manner that helps coworkers succeed, and enables colleagues to be accessible to one another.

Maybe it's a product of my compartmentalized mindset, I'm able to work through someone a few feet away talking about work things when asked about work things. It's when people have loud, echoing conversations about things not really relevant to the tasks at hand that I will HAPPILY concede to anyone who argues that those discussions should be taken elsewhere-like a break room or cafeteria if your office is equipped with one.

But two developers sitting next to each other, talking their way through a data validation issue, unless they're discussing it so loudly that it is legitimately obnoxious for two people whose faces are inches away from each other?

I'm not so sure this is such a work-shattering distraction as the implication seems to be from a majority of folks here-to the point where I'm inclined to call shenanigans and histrionics on the folks who can't function sans complete, utter total silence. The open office can die, in my opinion, but so does the idea that any instance of two people talking about work is just as, or close to being as unacceptable to the point of-as someone suggested-booking a conference room to have a 2 minute discussion when asked "How do I do x?".

[z0r]

I didn't use any hyperbole in my response, but you're projecting a lot onto mine. Let me give you a realistic personal example, something that might happen to me at least once or twice a week. I'm 20 minutes into establishing my bearings in a set of files I think I'll have to modify or at least understand for the next change I need to make. Someone comes over and asks me a technical question - maybe via a chat ping or a tap on the shoulder, or even just by walking behind me. Now I can choose to tell them it isn't a good time, but they've probably already started to describe their problem and that alone has stolen enough of the focus I was building up that I'm better off trying to help them first. (If I'm an hour in rather than 20 minutes in I'm more likely to tell them to ask me later). After giving them 5 - 10 minutes of my time, the original focus is lost. It may take me another 20 minutes just to get back to the cusp of beginning to write code again. There are only a few good sized blocks of time to work in the normal day, so that's more expensive than it seems.

I can deal with a nearby conversation and ignore it, although frankly it can be very distracting when it's about technical topics near my own work. Two or three at once is rarer but very irritating when it gets started up. Headphones are great for that, but when I'm suffering from tinnitus they no longer work. What's wrong with walking to a common space away from the work area when you want to have a 2 minute discussion with a coworker? If it's not worth the walk, maybe it isn't worth the discussion.

There's nothing strange about people having trouble in an open office space, all I would ask for is some empathy. I have internalized some of the lessons of my own problems by trying to resist the temptation to ping or otherwise disturb coworkers by non-email means unless it's absolutely necessary. A good deal of the kinds of questions I'm asked or I hear asked (maybe as many as half of them? and I would include my own questions here) could be solved by thinking or researching just a little more in solitude before reaching out.

I've also created improvised physical barriers around my desk to block visual distractions. As a result my current workspace is OK for getting things done, but it doesn't change the fact (for me) that open offices are bad by default and need personal and spatial modification to become acceptable, as compared to the mythical office with a door which would be good for getting things done by default. It's not about being incapable of function without "utter total silence", it's about being made slightly miserable every day on average.