cross-posted from: https://piefed.social/c/technology@piefed.social/p/2533091/proton-to-re-interview-staff-about-ai-to-see-who-gets-to-keep-their-job
cross-posted from: https://piefed.social/c/technology@piefed.social/p/2533091/proton-to-re-interview-staff-about-ai-to-see-who-gets-to-keep-their-job
If the code has been crafted correctly, none should be.
Client info should be 100% data, and remain 100% in production. If you have any dev-side data to test and debug with, it should be 100% procedurally-generated pseudo-data that only imitates client data in terms of gross patterns, and not specific points of data.
Like customer names. Those names should be broadly representative of what is found in the regions the software operates in, in order to demonstrate acceptable data input validation and effective storage compatibility with those names. For example, you don’t want to be storing European names in a DB field that is not UTF-8 compliant, or validating those names by restricting characters to US-ASCII. But any one generated name that just so happens to match an IRL name should be a statistical occurance, and any extended data attached to that entry should (generally) not match any other IRL data for any IRL occurance of that name…
Absolutely, sorry for misleading - we’re not a software company. We do engineer for medical devices so confidential information in this case covers most everything we deal with. It might be actual IP, which is less of a concern, but it might also be trade secrets which as much more sensitive!