I never thought code could be racist...
-
Indeed: my usual response is "No, but there is a 'U' in 'F**k Off'"
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
But there's a me in awesome. And the HR is continually wrong[^].
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
So I'm one of the A holes, problem is I'm the boss of the team!
Never underestimate the power of human stupidity RAH
-
I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:
What about "Dom" and "Sub" instead...? ;P
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
What about "Dom" and "Sub" instead...? ;P
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
--- This is me not making any comment ---
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
What about "Dom" and "Sub" instead...? ;P
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
What about "Dom" and "Sub" instead...? ;P
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I'll take the former, please. ;P
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:
Your management is being stupid. There's nothing intrinsically racist about master/slave, and although it's obviously wrong to put people in a position of slavery, there's nothing at all wrong with putting a machine in that state. Master/slave describes a particular type of relationship where the slave device does nothing except execute commands sent to it from the master, which primary/secondary doesn't adequately describe. If you have to change it, 'controller/worker' would be better. But really I just hate this sort of 'look at us we're being super diverse' PC nonsense.
-
That would be the intention! Just beware the "Dominator" pattern. It never ends well.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
JVonderharr wrote:
I work on a project that has devices which have a "Master" and "Slave" designation.
This was actually common terminology in the 1960s through 1980s, mostly for hardware, but with some leakage into software. Look at architecture details for the PDP-11 and VAX-11 for example. The Unibus has master/slave terms all over it (Bus Master, Slave Word Out, Slave Lower Byte In etc.) I think SCSI drives also have Bus Master as well to don't they? During the late 1970s, all software and new hardware architectures started using the terms "client" and "server", but existing architectures didn't change gratuitously. I was around then and don't believe that there was any intended racism involved ... it was more a small group of people being a little offended and perhaps some precaution from company's legal departments. Sort of like a sports team franchise nowadays. No way would you now see a new team with a name of 'Braves', 'Eskimos' or 'Redskins' but the existing teams aren't really changing (yet). Repeat after me - "client ... server". Feel better?
-- Harvey
Master/Slave and Server/Client really aren't the same at all. From Wikipedia: Master/slave is a model of communication where one device or process has unidirectional control over one or more other devices. In some systems a master is elected from a group of eligible devices, with the other devices acting in the role of slaves. The client/server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services.
Quote:
I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary.
Primary and Secondary is even worse. This all sounds like something out of Dilbert. Your project is doomed.
Jon CodeWrite
-
Indeed: my usual response is "No, but there is a 'U' in 'F**k Off'"
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
Or, there is a U in sunshine. I particularly like this one; I was in a meeting the other day and someone said "You know it seems to me that we have two ears and one mouth, so maybe we should talk less and listen more". To which I replied "Well you have two legs and one brain, so perhaps you should think less and fuck off more".
Every man can tell how many goats or sheep he possesses, but not how many friends. Shed Petition[^]
-
Or, there is a U in sunshine. I particularly like this one; I was in a meeting the other day and someone said "You know it seems to me that we have two ears and one mouth, so maybe we should talk less and listen more". To which I replied "Well you have two legs and one brain, so perhaps you should think less and fuck off more".
Every man can tell how many goats or sheep he possesses, but not how many friends. Shed Petition[^]
Monitor wipe to aisle 3!
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
JVonderharr wrote:
I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time.
More politically correct designation as variables' name can be "leader" and "team", HR would love it.
dev
-
I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:
JVonderharr wrote:
Have you checked for subtle hints of racism in your code lately??? :OMG:
Hyper-political correctness. The correct term is "master and slave", not primary and secondary. The nutcase who came up with the idea used two words with a vast different meaning than the original terms. Primary and secondary implies that the secondary structure equals the primary. Master and slave is not only undubious, it is very clear TECHNICAL language. The uneducated should not even try to understand those words and keep their hypocrisy to themselves. Even if it were a near-correct description, there is no-one who would be offended by the terms, their fakkin' part of history and you're not getting the blood of your hands by simply denying history. If anything, it's worse than the original. What ********* would recommend to change the source-code to reflect it being 'politically correct'?? Must be someone who is swimming in money and doesn't mind that tested code could be broken, by something that does not add any value whatsoever.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:
But Master-Slave and Primary-Secondary are two different concepts. :wtf: In Primary-Secondary, the secondary can work independently of the primary. If one breaks, the other takes over. But in a Master-Slave configuration, the Slaves are modules that depend on the Master. Slaves can work independently from other Slaves. But if the Master breaks, the Slaves stop receiving requests.
.
-
I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:
you are not alone from this silliness...
Charlie Gilley You're going to tell me what I want to know, or I'm going to beat you to death in your own house. "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Master/Slave and Server/Client really aren't the same at all. From Wikipedia: Master/slave is a model of communication where one device or process has unidirectional control over one or more other devices. In some systems a master is elected from a group of eligible devices, with the other devices acting in the role of slaves. The client/server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services.
Quote:
I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary.
Primary and Secondary is even worse. This all sounds like something out of Dilbert. Your project is doomed.
Jon CodeWrite
Jon Nethercott wrote:
Master/slave is a model of communication where one device or process has unidirectional control over one or more other devices...
The client/server characteristic describes the relationship of cooperating programs in an application...This distinction misses the point. In both cases, one device has unidirectional control over the other(s) and the relationship is cooperative. At any rate, no matter how you phrase it, the master/client makes requests of the slave/server which processes the commands on demand and both are otherwise mutually idle.
-- Harvey
