Magic pronouns considered harmful
-
It's not misogyny.
It is misogyny, and you claiming it's not makes you a male chauvinist pig.It seems you didn't bother actually reading a word I wrote, except just enough to create a juicy quote-out-of-context.
I read it, and maybe you are right, but you still would be called a misogynist by those people.Entirely replaced with all the shiny new code in SMOD #73.
The number is the identifier of SMOD in current setup. Your post doesn't make sense in this context.
-
Clearly I have yet to grasp the context.
How do your SMODs get their numbers allocated?
-
Again, I never said anything to contradict that.
If I may ask, which of these do you consider synonyms, and which are distinct: "shouldn't be fixed", "should be fixed never", "should be fixed, but has so low priority it will never get fixed because no one will bother"?
-
How do your SMODs get their numbers allocated?
Consecutive numbers, from 1 onwards. Currently up to 2 (used to be up to 1 for a long time).
-
shouldn't be fixed
Is a terrible attitude
@Gaska said:should be fixed never
Is the same
@Gaska said:should be fixed, but has so low priority it will never get fixed because no one will bother
Is better, but still not right.Let's improve it, shall we?
should be fixed, but has so low priority it will likely never get fixed because
no one will botherresources will be used to fix higher priority bugs insteadThat is… not great, but the best it can be given the practicalities of the real world.
-
So if you were in fact to see a gradual migration of functionality from the existing SMOD #1 to a new one, say SMOD #3, what would happen to the numbers when the new SMOD reached the point of completely superseding the old SMOD #1?
-
It is misogyny, and you claiming it's not makes you a male chauvinist pig.
What?
You could call it cisnormative and maybe even slap the "nonbinary erasure" label on it. But misogyny? No.
-
That is… not great, but the best it can be given the practicalities of the real world.
And what about low-priority bugs vs. high-priority features? Or vs. low-priority-but-still-needed-to-be-done-eventually features?What?
Welcome to feminist thinking.
-
Welcome to feminist thinking.
No, that's not how feminist/SJW nomenclature works.
See post that you replied to.
-
So if you were in fact to see a gradual migration of functionality from the existing SMOD #1 to a new one, say SMOD #3, what would happen to the numbers when the new SMOD reached the point of completely superseding the old SMOD #1?
No, not like that. Numbers are assigned at runtime, and refer solely to runtime configuration.
-
And what about low-priority bugs vs. high-priority features?
Depends. Will those features earn more money for the company? Yes? Do them first.
@Gaska said:Or vs. low-priority-but-still-needed-to-be-done-eventually features?
Bugs first, features after. The opposite to Discourse, basically.
-
Depends. Will those features earn more money for the company? Yes? Do them first.
Yes, they will. Same with the low-priority ones. On the other hand, fixing untriggerable bugs won't save any, ever.Bugs first, features after. The opposite to Discourse, basically.
Except you see the bugs in Discourse.
-
Numbers are assigned at runtime, and refer solely to runtime configuration.
Then I agree with you that using an arbitrary label for the start of the numbering, instead of just picking either 0 or 1 as seems most appropriate and just using that explicitly, is pointless wankery.
-
Except you see the bugs in Discourse.
Because no-one ever sees bugs in anything else ever
-
what's a SMOD?
Sweet Meteor of Death. One of the leading Republican candidates for 2016, currently battling it out with Cthulu.
-
@Gaska said:
Except you see the bugs in Discourse.
Because no-one ever sees bugs in anything else everBecause that's what he said
-
Because no-one ever sees bugs in anything else ever
If they never happen in practice, they don't.
-
Now, yes, but back in the like eighties or something it was a big deal. As I understand it the basic claim was that male was considered the default gender that everybody of value was assumed to be, and that people who made the prescriptive argument that @Stevethecynic is making were full of it because just mention a prostitute or housekeeper of unknown gender and watch what pronouns they start using.
-
"shouldn't be fixed", "should be fixed never", "should be fixed, but has so low priority it will never get fixed because no one will bother"?
None of those is synonymous with "not a bug", which was your original assertion
-
I just realized that @aliceif might have missed the joke.
-
that's what she said
-
-
None of those is synonymous with "not a bug", which was your original assertion
My original assertion wasn't meant to be taken literally. If it were to, then there's a logical contradiction in it, because I claimed that there's some possible interpretation of universum under which something that is an element of set A isn't an element of set A.
-
Was @gaska?
-
Neither was I. But I've made my friend to be pissed for me for two days for using gender-neutral "he" once, and it was back in 2013.
-
Well, I'm not gonna speculate about that then. All I wanted to say was that there were some strenuous arguments being made, back in the day.
-
There still are - but thankfully, most people manage to avoid them.
-
No thanks to you though :p
-
All aboard the !
-
I believe that's what they call "technological debt"?
Admittedly, caring about small details like this in an environment so full of bugs would be like caring about recycling paper while dumping toxic fuel in the river. But still.
-
Don't get me wrong. I love to work in good codebase. I strive for perfection in all my home projects. But my current work isn't a good place for that.
-
Does he really think it's more clear to say "SMOD #{FIRST_SMOD}" than simply "SMOD #1"?
Perhaps you should delegate that information to an expert system via a web service call over an enterprise service bus. Like that you wouldn't need to have anything hard-coded at all, and you'd be able to update all applications across the company (effectively) instantaneously. Boom! Infinite flexibility can be yours…
-
TIL about another HTML5 tag that shows middle finger to the whole idea of separating data from logic from presentation that's been going on for at least a decade now in HTML.
-
Non, pas du tout. I live in France, but I'm English.
-
Ah - mon bad.
-
Mówcie po angielsku, co?
-
Sí.
-
In case you didn't get it, it was in imperative mood.
Filed under: I feel very imperative today.
-
Do you know about the singular "them" and "their" and "theirs"?
That is a deeply awful usage.
-
Awful or not, this is what you have to use if you don't want to anger people.
-
That is a deeply awful usage.
Why? It comes completely naturally to any primary school student; it's the kind of thing that people generally need to be specifically trained not to do.
Personally I find it far more grating to hear somebody say "try and" when they mean "try to".
-
their their. Its not to bad once you accept that for all intensive purposes less people get things wrong then you think. Jest try not to let it effect you
-
once you
acceptexcept that for
@Jaloopa said:less people get things wrong then you
thinkthing.BTFY
-
-
BTFY
I think my internal grammar Nazi stops me from completely mangling any given sentence. That was painful enough as it was
-
@Steve_The_Cynic said:
It's not misogyny.
It is misogyny, and you claiming it's not makes you a male chauvinist pig.
No, saying that English has a perfectly serviceable pronoun for "person of unknown or unspecified sex", and that that pronoun is "he", is NOT misogyny. Telling you something you don't want to hear isn't misogyny, and you insisting that it is makes you misandrist.@Steve_The_Cynic said:
It seems you didn't bother actually reading a word I wrote, except just enough to create a juicy quote-out-of-context.
I read it, and maybe you are right, but you still would be called a misogynist by those people.
So what? They're wrong.
-
That is a deeply awful usage.
Meh. Six of one, half dozen of the other. I've used both. You're either "wrong" on quantity or gender.
-
what he wrote
Wait, isn't RaceProUK female?
Edit: Hanzo'd. I really should learn to read the rest of the thread...
-
Says so on my profile ;)
-
From now on, when referring to @RaceProUK, I'll use "zee" and "xir" pronouns. Better to be on safe side and not assume any of 78 genders, even if zee explicitly states which one zee identifies with - who knows what it will be tomorrow?