3 ms·

the salaries of a good CFO and a few lawyers.

• phamilton 11y ago
  As an engineer at a company recently acquired by a public company, we had a decent amount of work to do to become compliant. Code review, deploy procedure, etc all needed to be documented and formalized. These weren't too difficult, but they definitely tied up engineering resources for a decent amount of time.
  • batbomb 11y ago
    Yeah, my impression is that if you are a decently organized company it's a piece of cake. If you have mountains of technical debt, spaghetti code and no build processes, dozens of SaaS products, zero documentation, piecemeal authentication/security, etc... it can becomes quite onerous.
    • phamilton 11y ago
      For us it was a lot of simple things. Change management was the biggest pain but in the end it was just an extra step in our build process. Our canary process was a bit hands on (find a host, deploy to that host, tcpdump/check logs to validate the changes were correct and in effect). We stopped doing that. I can't decide if we are building better software without that as a crutch or if we are just not seeing production issues. Anyway, it's stuff like that. Little shortcuts here and there. Nothing major, but it required behavioral change within the org.