I'm working on automating a repetitive task that I need to run hundreds of times.

I took a look at the source code for some hints about which REST API functions might be useful and I saw this gem right at the top of the file:

Quote:

---

/*
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
*/

---

We're not talking about calling architecture components Master and Slave or something like that.
This is in the source code where nobody is ever going to look. Wow.

For the people who are fans of this type of pointless virtue signaling:
Does this harm me in any way? NO
Is it pointless and stupid? YES

NEWSPEAK

Our new AI overlords are being taught to be PC. Just wait until flying robots ask us our preferred pronouns before forcing us into hard labor.

Wait

Whats wrong with using the terms master & slave to describe components?

1984 was a how to manual, not a fictional novel.

My Name Is Judge said:

---

Wait

Whats wrong with using the terms master & slave to describe components?

---

Oh, there's a long list that's been running around the IT industry for the past two decades.

Master and Slave - obviously means American Slavery - therefore Black people are inferior, less than, etc. These terms have been discouraged in favor of terms like Primary / Secondary, or Independent / Dependent, etc.

Whitelist / Blacklist - again, infers denying access to Black people. At my company, this has been changed to allow list / deny list.

What's funny about many of these terms is that they don't have any context relevance to the Indian programmers who wrote them. But once White management and White marketing people in the Silicon Valley find out about them, they make the Indian guys do re-writes and renames.

With respect to not breaking existing functionality, we took white list / black list out of the graphic user interface but, the process for gaining access to download the latest version of software that's not ready for prime time yet, is still called - whitelisting.

edit, listed above .... sounds like BQ and I might work for the same company...

Foamcows said:

---

edit, listed above .... sounds like BQ and I might work for the same company...

---

There's only one other Aggie that I'm aware of at my company. Do you work a lot in downtown HTX and just bought an acreage property out near Sommerville?

HollywoodBQ said:

---

I'm working on automating a repetitive task that I need to run hundreds of times.

I took a look at the source code for some hints about which REST API functions might be useful and I saw this gem right at the top of the file:

Quote:

---

/*
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
*/

---

We're not talking about calling architecture components Master and Slave or something like that.
This is in the source code where nobody is ever going to look. Wow.

For the people who are fans of this type of pointless virtue signaling:
Does this harm me in any way? NO
Is it pointless and stupid? YES

---

so you work for a to big to fail bank?

Quote:

---

For the people who are fans of this type of pointless virtue signaling:
Does this harm me in any way? NO
Is it pointless and stupid? YES

---

While it doesn't physically "harm" you in any way.... someone (or more than one) with a degree in some useless LA gender studies program is getting paid. This useless crap costs you money indirectly by siphoning money directly from your company (which affects your income).

Ag87H2O said:

---

1984 was a how to manual, not a fictional novel.

---

I doubt seriously Orwell was writing that book as a how to manual. It was a warning.

Texas Yarddog said:

---

Quote:

---

For the people who are fans of this type of pointless virtue signaling:
Does this harm me in any way? NO
Is it pointless and stupid? YES

---

While it doesn't physically "harm" you in any way.... someone (or more than one) with a degree in some useless LA gender studies program is getting paid. This useless crap costs you money indirectly by siphoning money directly from your company (which affects your income).

---

No doubt. I'm having a hard time trying to hire a few people to perform customer facing roles.

But... we're damn sure required to do a bunch of diversity training and we've just gone through BHM and Hispanic Heritage month, etc. I think it's women's month now.

HollywoodBQ said:

---

I'm working on automating a repetitive task that I need to run hundreds of times.

I took a look at the source code for some hints about which REST API functions might be useful and I saw this gem right at the top of the file:

Quote:

---

/*
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
*/

---

We're not talking about calling architecture components Master and Slave or something like that.
This is in the source code where nobody is ever going to look. Wow.

For the people who are fans of this type of pointless virtue signaling:
Does this harm me in any way? NO
Is it pointless and stupid? YES

---

If you were to remove the code, could that be traced back to you?

We're all for removing it. Yesterday.

I hate virtue signaling in code comments. It has zero informative value to others using the code. I also still use the terms whitelist and blacklist. They are very descriptive of what you are wanting to do with those types of arrays.

Coders used to have senses of humor. So you'd find funny stuff or interesting naming conventions.

Now we have this? Pathetic soy boy routine is my guess