Classic programming terminology preservation. - Keep Sociology out of the Sciences - Share experiences and techniques around preservation of original programming terminology.

Jotch

Well-oiled and ready to last for the long-run
True & Honest Fan
kiwifarms.net
Joined
Dec 15, 2022
At my workplace there is an increasing push to remove terms like "Whitelist/Blacklist" and "Master/Slave".

As the old guys continue to retire there is less and less force holding these traditions in place.

I would prefer to keep around the original terminology and culture of computer programming, does anyone else have experiences with this?
 
Trying to erase blacklisting/whitelisting is the most straightforward and obvious racism self-report I've yet to see. Same goes for master/slave, but with literal fucking primary colors that were used as metaphor since the dawn of fucking time you don't have any excuse for inserting back-asswards race delusion. The natural sperg response is to replace blacklist/whitelist with jewlist/europeanlist.

I'd rather general technical terminology preservation. Kill all atheistcucks who supposit Anno Domini for Christ Entered, kill all redditors who take the onkey out of monkeypox, and gas all jews who wish to remove the contributions of NSDAP German scientists. Glory to Hans Asperger and his syndrome, Hans Eppinger and his spider nevus, Max Clara and his cells, Friedrich Wegener and his granulomatosis, Walter Stoeckel and his operations, sutures, Franz Seitelberger and his disease, Hans Joachim Scherer and his syndrome, Julius Reiter and his arthritic disease, Hugo Spatz and his reaction, Murad Jussuf-Bey Ibrahim and his disease, and Julius Hallervorden and his syndrome, may you live forever through your work.
 
Not witnessed it at work, but I have seen it happening elsewhere. At some point Firefox replaced 'Master Password' that you have to enter before any of your saved passwords will autofill with 'Primary Password'.

I hate this, not just because it's pointless, but because like so much newspeak it only makes things harder to understand. Master Password was clear: it was the password you entered to gain access to all other passwords, like a master key that opens all doors. Primary Password is unclear, because it only indicates it's the first stage of a multi-step process, like 2FA. How many passwords will I need to enter after the primary one? Who knows!
 
It's a long shot, but if your company has any contracts with the US government, you could file a anonymous report. This is the type of shit Trump's anti woke E.O.s were meant to combat. After a few threats from the federal govt revoking their cushy contracts companies will be willing to rename them anything short of niggerlists.
 
tfw the country you live in doesn't care about this bullshit
smug horse.webp
 
Each time that i make git repo either for myself or company that i work at i ensure that the master branch is called properly. Fuck communist newspeak.
i think git still configure new repositories with a master branch by default it just makes a gay warning or whatever
 
Gitgud defaults to master
 
i think git still configure new repositories with a master branch by default it just makes a gay warning or whatever
Yes. On Windows it'll ask you what your preference is and the "Let Git decide" option means master for now, possibly main at a later unspecified date. It has said that for at least a few years now and it baffles me why they don't just set a hard date for their switchover or just abandon the effort and leave the git default as master.

Of course any self respecting individual overrides the default so it's "master". My colleagues are a bit git illiterate so I had to write guides on how to install it correctly on Windows (i.e. configure it to use Schannel, HTTP proxy settings, etc.) and one sneaky step I put in there was explicitly configuring git to use master as the default branch.

It's your duty as a sperg to hardcode the use of master/slave and whitelist/blacklist everywhere. It mustn't be easy enough to excise that an intern programmer can "correct" the verbiage with sed. It must be baked into the schema of every config, hardcoded into columns of tables, so thoroughly ingrained into the design of your project that to remove it would be a monumental effort causing an endless list of breaking changes.

Another thing I have considered is a kind of essential string of characters. A sequence of something, like say... Nigger, which random components will call upon to do unrelated work. Something which if removed, would make basically every class in the IDE light up red. That way the Nigger is preserved no matter what as nobody wants to try and figure out why billing.php depends on it. Bonus points if serious errors could cause Nigger to be exposed to the end user.
 
wokerotting terms is pretty bad, but there is another type of replacement going on too.
  • every time i say hacking i have to specify that i mean it in the MIT sense
  • memory units have been circumcised to match powers of 10 (kibibyte and such had to be introduced)
  • inversion of control is now something your java framework does with your object initialization
  • unit test means any kind of test
  • artificial intelligence refers to machine learning only and recently even that is narrowing down to LLMs
  • processor word now marks 2 bytes because intel said so
  • DOS is equivalent with DDOS-ing a server.
  • a javascript array is just a vector... or list depending on who you ask, but most definitely not an array
for each of these, thing was publicized about or straight up marketed without context or explanation, then the new meaning gained critical mass and you can no longer express yourself clearly because the meaning others know is a coin-toss.
 
Back