Re:ASCII Boobs in Your Codebase Won't Fix Themselves
by LinuxBender on Monday November 04, 2024 @12:07PM
(#42043616)
In my opinion this is no more taboo than changing master / slave to primary / secondary, a known pattern in tech. Times change, documents and code get revised to reflect the changes. Having been in a highly audited environment one might have a quick meeting with the heads of compliance, legal and maybe HR if people are having challenges. Let them sign off the changes and add a comment in the change control system if there is a concern. This should especially be a non issue if the ASCII contributor has already left the company.
[ Parent
| on HN ]
Re:ASCII Boobs in Your Codebase Won't Fix Themselves
by jeffrey-sherman on Monday November 04, 2024 @12:27PM
(#42043853)
Yes, you should go talk to compliance.
But for a lot less effort, you could ignore it and talk to no one.
Re:ASCII Boobs in Your Codebase Won't Fix Themselves
by LinuxBender on Monday November 04, 2024 @12:43PM
(#42044044)
Yes, you should go talk to compliance. But for a lot less effort, you could ignore it and talk to no one.
Pulling together that meeting would only be if someone is complaining. That's what I meant by people having challenges. The goal being to head it off before it turns into a internal chat system flame-war or an HR issue that tries to single people out for blame. Hopefully people at the top will not be concerned for petty issues and are professional enough to put it to rest. It is a normal part of a companies maturing process.