I have to remind myself not to read too much into such things, for three reasons that we all know, but which may bear repeating to oursel...
I have to remind myself not to read too much into such things, for three reasons that we all know, but which may bear repeating to ourselves: 1. Open source is global, and not everyone is a native speaker of English. 2. Among English speakers, not everyone has the same cultural conventions and nuances. Even within US cities, you can drive 15 minutes, and find very different conventions. And culture in Boston isn't the same as in the Bay Area, isn't the same as in Bolivia. 3. Even within the same culture, not everyone picks up on signals in language to the same degree (whether perceiving or sending). And some people who think they're picking up on signals are conflating with biases more than some others do. I say I have to remind myself, because this still hits me. For example, when I'm searching certain bug databases, trying to solve an annoying problem, and some prolific volunteer commenting on a bug report there speaks in a manner that comes off as brusque or dismissive. Where they're from (across the Atlantic from me), maybe it's interpreted as professional or capable, and is even reassuring.
Posted by neilv on Jul 30, 2023, 2:33 AM
Tags
Related issues
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
- > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
hackernews (Other)
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
The biggest problem with plugging a generator into an outlet is you need a double ended cord.
I have to remind myself not to read too much into such things, for three reasons that we all know, but which may bear repeating to oursel...
I have to remind myself not to read too much into such things, for three reasons that we all know, but which may bear repeating to ourselves: 1. Open source is global, and not everyone is a native speaker of English. 2. Among English speakers, not everyone has the same cultural conventions and nuances. Even within US cities, you can drive 15 minutes, and find very different conventions. And culture in Boston isn't the same as in the Bay Area, isn't the same as in Bolivia. 3. Even within the same culture, not everyone picks up on signals in language to the same degree (whether perceiving or sending). And some people who think they're picking up on signals are conflating with biases more than some others do. I say I have to remind myself, because this still hits me. For example, when I'm searching certain bug databases, trying to solve an annoying problem, and some prolific volunteer commenting on a bug report there speaks in a manner that comes off as brusque or dismissive. Where they're from (across the Atlantic from me), maybe it's interpreted as professional or capable, and is even reassuring.
Comments (0)
No comments yet. Start the discussion.