4 ms·

working on non-version-controlled code, having been expressly forbidden from using ANY VC by the CEO Did the CEO give a reason? I'm a bit curious based on it

• etxm 7y ago
  HIPAA
  • reificator 7y ago
    I don't work with HIPAA but with other compliance/regulations NOT using version control is the problem. Unless you have patient information hardcoded into the source code for god knows what reason...
    • marrone12 7y ago
      Things that might be hardcoded are access keys and passwords to PII databases.
      • rovr138 7y ago
        Which is bad practice for lots of reasons and, is that a HIPAA violation? Your code also has it then. Hosting git externally might be an issue though.
      • all_usernames 7y ago
        No. No no no no no.
  • other_herbert 7y ago
    You're not storing patient details in VC...... Right? Maybe show him that you can run svn even on his own machine... Anything... Anything is better than not using something
  • technomike 7y ago
    I've work with HIIPA and VC. No issues, as long you do not store patient information within the source code, I cannot think of any reason why you would need to do that...
  • protomyth 7y ago
    I worked at a place that is extremely concerned with HIPPA to the point of having many specialist lawyers. We were required to use version control.
  • sergiotapia 7y ago
    I work with HIPAA and SOC2, this is ridiculous. Your boss is misinformed. Just show him that you're literally only committing code, and not any real data in the repo.
• rjplatte 7y ago
  CEO doesn't like "the cloud", and VC is obviously that to him. I do use it locally, but that's about all. Yes, I just wrote an EDI exporter in Ruby for Medicaid services, working on one for MCOs now. Thankfully we don't have to import EDI, or I'd go nuts.