Around page 28-29, you'll find the Court's opinion on Sarbanes-Oxley and its future. In short, it appears they strike down a provision that allows the executive branch to remove a member from the board of directors, leaving the rest of the law intact. Apologies in advance, and please correct me - I'm neither a lawyer or an expert on Sarbox. [Edit: See comment below by kgrin] This seems to be the most relevant portion…
they strike down a provision that allows the executive branch to remove a member from the board As with another sibling comment, you've got it exactly backwards. The Court struck down a clause that limited the ability of the President/SEC to remove members. The President now has greater discretion, not less.
Supreme Court Strikes Down Part of Sarbanes-Oxley
21–25 of 25 posts
Re: Supreme Court Strikes Down Part of Sarbanes-Oxley
#22Earlier quoted context omitted.
Any communication between employees must be archived and stored in some super-special repository. Any tool that doesn't store its data in said super-special repository is a crime to use. I'm surprised we don't have to record our in-person chats with a wearable video camera.
Do these super-special repositories have a decent API?
Basically, it is the same story as almost all enterprise software: abandon all hope ye who enter here.
Re: Supreme Court Strikes Down Part of Sarbanes-Oxley
#23Re: Supreme Court Strikes Down Part of Sarbanes-Oxley
#24Earlier quoted context omitted.
Do these super-special repositories have a decent API?
This type of tool puts the capital E in Big Freaking Enterprise. Not only do they not have decent APIs, to the extent that they do have APIs at all they're written in whatever the best practice was for Java architecture astronauts 10 years ago (I say that with as much love as I can muster, having been one), and the API is not laid out according to programmer utility but rather according to ossification of business pr…
Re: Supreme Court Strikes Down Part of Sarbanes-Oxley
#25Earlier quoted context omitted.
This type of tool puts the capital E in Big Freaking Enterprise. Not only do they not have decent APIs, to the extent that they do have APIs at all they're written in whatever the best practice was for Java architecture astronauts 10 years ago (I say that with as much love as I can muster, having been one), and the API is not laid out according to programmer utility but rather according to ossification of business pr…
Why does enterprise software so rarely have good APIs?