News for hackers. Stuff that matters.
Re:Silicon Valley's $585B Problem by vasilipupkin on Friday April 22, 2016 @09:41AM (#11549041)
I am always frustrated by this 0 or 1 line of reasoning. "I don't believe Sarbanes Oxley has anything to do with companies not going public". So, you seriously believe that regulation that raised the cost of going public has contributed literally zero to the reduction in IPOs? I mean is it the only sole cause? No. But should it get zero weight? no
Re:Silicon Valley's $585B Problem by chollida1 on Friday April 22, 2016 @09:48AM (#11549110)
Ok, how about I rephrase this, I don't think there is a single company that would be successful as a public company that has chosen not to go public due to Sarbox.

What Sarbox did was to put into law what companies should have already been doing in terms of corporate governance and financial reporting.

The companies that consider thsi to be a burden were ones who are already doing either shady things with their accounting or who just weren't doing proper oversite to begin with, hence the small number of companies who where complaining about it when it first came out.

Should Sarbox regulations get zero weight wrt to stopping companies from going public?

Yes I believe its impact is so minuscule that you can give it zero weight.

Re:Silicon Valley's $585B Problem by vasilipupkin on Friday April 22, 2016 @09:58AM (#11549212)
what is the cost of Sarbanes-Oxley compliance to the company in dollars ?
Re:Silicon Valley's $585B Problem by phkahler on Friday April 22, 2016 @10:48AM (#11549584)
I'd prefer the cost in humans. How much staff does it take to ensure compliance. That's helps you figure out what size the company has to be since you might have to hire a few people. For a 500 person company it's no big deal.

How big was Cruise when GM went to buy them? I think too small to have done an IPO and part of that is that they were too small to have hired the extra people for compliance.

Re:Silicon Valley's $585B Problem by nopzor on Friday April 22, 2016 @10:59AM (#11549673)
It costs few million dollars a year just to be a public company, SOX compliance included.
Re:Silicon Valley's $585B Problem by batbomb on Friday April 22, 2016 @10:22AM (#11549399)
the salaries of a good CFO and a few lawyers.
Re:Silicon Valley's $585B Problem by phamilton on Friday April 22, 2016 @11:25AM (#11549862)
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.
Re:Silicon Valley's $585B Problem by batbomb on Friday April 22, 2016 @01:59PM (#11551093)
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.
Re:Silicon Valley's $585B Problem by phamilton on Saturday April 23, 2016 @11:49AM (#11556024)
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.

Re:Silicon Valley's $585B Problem by saosebastiao on Friday April 22, 2016 @11:12AM (#11549770)
There's an accounting cost, but it's the tip of the iceberg. The real costs add up when even entry level employees (like myself working for a Fortune 500 out of college) hit major roadblocks in developing simple solutions to simple problems because a lawyer or auditor shows up and throws a Sarbox fit.