3 ms·

Is no one else put off by the tone of this article? The author comes off like some kind of bitter incel who has already decided that all women are bitter, miser

Is no one else put off by the tone of this article? The author comes off like some kind of bitter incel who has already decided that all women are bitter, miserable hags that snicker at "nerds". Extremely cringe and a very poor way to try to get your point across.

dogleash 5y ago
>Is no one else put off by the tone of this article? Not really, it's just a more personal retelling of something anyone in a skilled domain knows exists. If I were to tell a more professional version of the same phenomenon, I'd make it a story about cross functional collaboration at the office. There are two major categories to those interactions, the first where the differently-skilled people respect and understand the complexities of each-others' domains, and understand the point is to bridge that gap. Then there are those who are annoyed that a problem has strayed into a skillset they don't have, and make it quite visible that they're annoyed it's not already a solved problem (without the context to know if it's something reasonable to expect to already be solved and/or care to learn if it's actually something quite easy they could do on their own). And it's not about software skill. The first time people interact with our legal department, it's usually because they were asked to send documents over for feedback, and just shoot them over cold. The first phone call with one of the lawyers is the "freebie" where they're forgiven for not reading the documents to the best of their ability first. The lawyer teaches our team members enough about what they're looking for and how to annotate documents with what is/isn't relevant to the business context of the documents and whatever technical background they need before sending them over. On the other hand, we have people who are deep into one technical field and have day-to-day dependencies on something only slightly outside their wheelhouse. When they hit a wall and ask for help they'll often get if from someone who loves the thing, will talk your ear off about it if you let them, and really like teaching people about the thing. But the person asking for help has already mentally shutdown and are too exasperated to learn anything as they go. Helping laypeople with technical issues is often interacting with someone who's (at best) coming from a helpless and defeated position. It's not their fault, it's just the way society teaches people to think about tech. But it does breed resentment towards the people they have to rely on, and on top of that it's already uncool to know about the stuff. You sorta have to be blind not to see the "just give me the answer and then fuck off forever" attitude from many people that hate the fact they're seeking your help. It's why I feign ignorance on many technical matters outside work ("no, my job involves different kinds of computers and I have to go our IT department for this stuff too").
Dma54rhs 5y ago
Living experiences are valid.

dogleash 5y ago

>Is no one else put off by the tone of this article? Not really, it's just a more personal retelling of something anyone in a skilled domain knows exists. If I were to tell a more professional version of the same phenomenon, I'd make it a story about cross functional collaboration at the office. There are two major categories to those interactions, the first where the differently-skilled people respect and understand the complexities of each-others' domains, and understand the point is to bridge that gap. Then there are those who are annoyed that a problem has strayed into a skillset they don't have, and make it quite visible that they're annoyed it's not already a solved problem (without the context to know if it's something reasonable to expect to already be solved and/or care to learn if it's actually something quite easy they could do on their own). And it's not about software skill. The first time people interact with our legal department, it's usually because they were asked to send documents over for feedback, and just shoot them over cold. The first phone call with one of the lawyers is the "freebie" where they're forgiven for not reading the documents to the best of their ability first. The lawyer teaches our team members enough about what they're looking for and how to annotate documents with what is/isn't relevant to the business context of the documents and whatever technical background they need before sending them over. On the other hand, we have people who are deep into one technical field and have day-to-day dependencies on something only slightly outside their wheelhouse. When they hit a wall and ask for help they'll often get if from someone who loves the thing, will talk your ear off about it if you let them, and really like teaching people about the thing. But the person asking for help has already mentally shutdown and are too exasperated to learn anything as they go. Helping laypeople with technical issues is often interacting with someone who's (at best) coming from a helpless and defeated position. It's not their fault, it's just the way society teaches people to think about tech. But it does breed resentment towards the people they have to rely on, and on top of that it's already uncool to know about the stuff. You sorta have to be blind not to see the "just give me the answer and then fuck off forever" attitude from many people that hate the fact they're seeking your help. It's why I feign ignorance on many technical matters outside work ("no, my job involves different kinds of computers and I have to go our IT department for this stuff too").

Dma54rhs 5y ago

Living experiences are valid.