Misc: Technology industry new terminology initiative


Summary:
I've been working in technology for about 20+ years now, so it'll be difficult for me to break old habits w/ terminology, but I'm posting this here in the hopes that I can continue to adjust to new dynamics.

Nothing really technical here, but if you happen to commit/modify code anywhere, here is a good starting point to adjust the terms you use in your code.  Also, a reference point to adjust your spoken vernacular to be inclusive to all those around you.

Information shared from the VMware vExpert program.

Words

Recommended Alternate

Other Situational Alternates if Recommended Alternate does not work

abort

stop

·         cancel

·         halt prematurely

·         end prematurely

·         stop prematurely

blacklist

·         denylist (n)

·         block (v)

deny (v)

blackout

·         restrict (v)

·         restriction (n)

outage (n)

kill

stop

halt

master

primary

·         main

·         original

·         control plane / control plane node in Kubernetes context

rule of thumb

rule

guideline

segregate/segregation

·         separate

·         separation

slave

secondary

replica

whitelist

·         allowlist (n)

·         allow (v)

·         safelist (n)

·         acceptlist (n)

Other Terminology Recommendations

Terminology changes/guidelines going forward (no legacy changes)

No change needed

Words

Alternates

Words

black hat

unethical

·         bind/binding

·         black box

·         black hole

·         black screen

·         invalid (adj)

·         masterful

·         mastermind (n, v)

·         masterpiece

·         master plan

·         masterstroke

·         simple

·         white board

female

·         jack (n)

·         socket (n)

he ***

they

eviction

alternate usage depends on the situation

execute

run

ghetto

TBD

kill switch

TBD

male

plug

she ***

they

suffer **

alternate usage depends on what's being described; alternates can include:

·         decrease, lessen, shrink

·         increase, grow

taint

TBD

white hat *

ethical


Comments

Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more