News for hackers. Stuff that matters.
Re:Why do programmers need private offices with doors? (Do N... by laserlight on Tuesday December 19, 2023 @04:35AM (#38693608)
> mildly inconvenienced

Judging by GP comment, they sound like they are heavily inconvenienced. Am I reading it wrong?

Re:Why do programmers need private offices with doors? (Do N... by cauch on Tuesday December 19, 2023 @04:42AM (#38693646)
I'm pretty sure that if you write down a list of inconveniencing things, this cannot be anywhere but at the bottom. The fact that some person will cry and shout that it is very very inconvenient seems to just confirm this person is acting like a toddler.

But in fact you are right, "mildly inconvenient" may not be the best way to put it, it could have been "because otherwise you are as inconvenienced as they are if they follow your wish". After all, that is my point: I don't say it's not inconvenient for you, I'm just asking why should a group prefer the solution where A is inconvenienced and B not inconvenienced over a solution where B is inconvenienced and A not inconvenienced.

Re:Why do programmers need private offices with doors? (Do N... by ath3nd on Tuesday December 19, 2023 @06:07AM (#38694182)
> After all, that is my point: I don't say it's not inconvenient for you, I'm just asking why should a group prefer the solution where A is inconvenienced and B not inconvenienced over a solution where B is inconvenienced and A not inconvenienced.

There is a simple difference here. We have:

- a person who HAS the knowledge

- and we have a person who WANTS the knowledge

Let the person who has the knowledge decide how to teach it to the person who wants it. DEMANDING that the knowledge is given to them, pronto, is not the proper, or even ethical way, to approach this.

If I wanted something out of you, and you need to take of your time to give it to me, I sure as hell shouldn't act like YOU owe me something. And yes, that's within a work context, so I won't say no, it's a part of my job to teach you, but still one side is taking, and one is giving. The side that's giving is the one that determines how the dissemination of knowledge will be done,. In this case, I want you to come to me only after you have distilled your questions to a coherent list and scheduled a meeting with me and added the questions to the agenda. That allows me to prepare with materials, have clarity in my head how to approach your teaching, etc.

You are not a toddler that needs constant handholding, you are a grown adult starting in a company, so try to act like one and have a coherent agenda and questions and search at least a bit for answers before going to the parental figure with your questions.

That's it, that's how it's gonna be, deal with it and stop crying!

Re:Why do programmers need private offices with doors? (Do N... by cauch on Tuesday December 19, 2023 @06:20AM (#38694282)
Hm, one could as legitimately argue: if the person who has the knowledge FAILED to document it properly and give it to the person who needs it. Then the person who has the knowledge is the one who deserve to have their flow disrupted instead of the person who notice they haven't done their work. Why should the person who demands the knowledge pays for the other person failure?

But more importantly, a grown-up would say: the two persons are collaborating, they are not fighting each other. The person who has knowledge is a grown-up, they will want the work to progress correctly and they will want to see their colleague succeed professionally and socially. The person who needs the knowledge is a grown-up, they will not ask over and over again when they see it disturbs the person who has the knowledge (and no one here is against that, obviously).

That's a sad way of seeing professional relationship, but also not a very smart way too: in real life, your own position is biased: when Mr X asks Mr Y a question, it is because Mr X truly believe it's a legitimate question. But maybe Mr Y has written the doc somewhere and Mr X missed it (which can and will happen). In which case, Mr Y will think Mr X is "wrong". But how Mr X can be sure he is not "wrong": Mr X does not know what he does not know. Or maybe Mr Y has written the doc, but badly. In which case, Mr Y will incorrectly think Mr X is "wrong". Or maybe ...

In short: grown-ups understand that communication is messy and that "counting points" is just ridiculous, inefficient and just something that a person who has poor understanding of the reality will think is fine.

Re:Why do programmers need private offices with doors? (Do N... by ath3nd on Tuesday December 19, 2023 @06:51AM (#38694472)
> if the person who has the knowledge FAILED to document it properly and give it to the person who needs it. Then the person who has the knowledge is the one who deserve to have their flow disrupted instead of the person who notice they haven't done their work

Hard agree!

> But more importantly, a grown-up would say: the two persons are collaborating, they are not fighting each other. The person who has knowledge is a grown-up, they will want the work to progress correctly and they will want to see their colleague succeed professionally and socially. The person who needs the knowledge is a grown-up, they will not ask over and over again when they see it disturbs the person who has the knowledge (and no one here is against that, obviously).

Hard agree!

> In short: grown-ups understand that communication is messy and that "counting points" is just ridiculous, inefficient

Agreed. However, as engineers, if we see communication within the team being messy, you also need to judge is that okay, or could we improve it, by setting some ground rules or improving some process or maybe having more dedicated sessions for creating a good shared understanding. OP's thread, it felt to me, thought that messiness in communication was solvable only by being on-prem and able to ask quick questions, while I am convinced it can be solved far more elegantly and with less overall effort with a good, focused onboarding experience and even (or especially) in remote settings.

Re:Why do programmers need private offices with doors? (Do N... by broscillator on Tuesday December 19, 2023 @10:29AM (#38696787)
Emotions are running high in this comment.

I think it doesn't really have much to do with what anyone wants. It's funny that I am inclined to think OP would be annoying, but this comment almost is doing the opposite of what you intended and swaying me the opposite way. Knowledge should be shared, and not under a list of very capricious conditions.

But, I get it, that's how you work and we've all got our things. I've never worked at an office, and I'm just realizing that all the discussions here could be solved by simply having a guy like OP paired with a guy who enjoys sharing their knowledge and unblocking these problems ASAP. A people person, which I get coders tend not to be. A guy whose flow is that, not just being an island out of a krazam sketch.

Re:Why do programmers need private offices with doors? (Do N... by 8n4vidtmkvmk on Tuesday December 19, 2023 @05:42AM (#38694035)
I think one is more inconvenienced than the other. If someone doesn't answer your question immediately, search harder. The answer is out there somewhere.