4 ms·
Clearly we differ on how we feel about approaching people. I’d rather get a simple message. When people have to write things they tend to think more about wha
by frumper 3y ago
Clearly we differ on how we feel about approaching people. I’d rather get a simple message. When people have to write things they tend to think more about what they want to say. And what you’re describing about the fly on the wall is still simply they aren’t communicating well if they aren’t including coworkers that may only be included for the benefit of learning how to handle situations. One way to handle that is to approach your boss and ask to be included in those situations because you’d like to learn how to respond. Your last line sums up how you feel about remote interactions nicely. I’m sorry, I just don’t find that your feelings about online rejections is a good enough reason to drive into an office.
- rcme 3y ago> And what you’re describing about the fly on the wall is still simply they aren’t communicating well if they aren’t including coworkers that may only be included for the benefit of learning how to handle situations. One way to handle that is to approach your boss and ask to be included in those situations because you’d like to learn how to respond. That's kind of the point though. When you're together, you don't need to think about how to include others in the discussion or talk to your manager. It all happens organically. > I’m sorry, I just don’t find that your feelings about online rejections is a good enough reason to drive into an office. Again, this is not my personal feeling. I ran a video conferencing company that served hundreds of thousands of people over the pandemic. I'm telling you the feedback we got from our users. So, you might not be willing to drive to an office for my feelings. But if you're not willing to drive to an office for the majority of your team's feelings, you might just be an asshole?
- frumper 3y ago> There is always an element of rejection when it comes to approaching someone online. If your primary reason for wanting to be in office is fly on the wall lurking and not wanting to feel rejected then those aren't very good reasons. Ask to be apart of solutions, groups, teams, emergency responses and projects. You'll learn 10x as much working with those co-workers to solve the problem than you would by listening to some coworkers doing it. > So, you might not be willing to drive to an office for my feelings. But if you're not willing to drive to an office for the majority of your team's feelings, you might just be an asshole? I work in a group of 10 developers and 0 out of 10 want to be in office, but hey, I don't mind if you want to take shots at me. I'm not against working in an office, I just want to have real reasons why it's needed.
- 8note 3y ago> when people have to write things they tend to think more about what they want to say. This is the bad part -- the best stuff to learn from has been filtered out. Text is written with a specific audience in mind, and that audience generally isn't students. You can write a second document sure, but that requires dedicated tome to writing a second document, and even then, the author may not know which details are most important for the student to know
- frumper 3y agoHey, are you busy? Or Can we chat about a problem I’m having with the dev server? Or When do you think you’ll have free time? Those questions are all direct and to the point. They didn’t start out with “hey, see the raiders game last night, it was crazy. My dog was so excited from all the yelling she jumped on the table and started eating the chips.” To be clear. We were talking about reaching out to coworkers.