4 ms·

None of these were the kind of bug that comes from releasing code with insufficient testing. The only one that even involved code was the Reddit password probl

• neilk 18y ago
  A culture of testing is a lot more than just verifying functionality. Code reviews with experienced engineers would have caught that design flaw before it was released. Or made it a high priority to fix. I've dealt with the security teams at large companies. They end up implementing sometimes draconian policies, but it seems that programmers refuse to learn to write secure code any other way. I have to admit that, if you consider the large company as being a legitimate entity, they're doing legitimate work.
• shiro 18y ago
  Privacy breach could harm a company a lot. Japan Network Security Association reported that, in 2007, total of 30 million personal information records are breached and estimated 22 billion dollars for damage/compensation in Japan. Most of these incidents caused by employees taking out the data, but there are some cases caused by sloppy web app. (I could find only Japanese version of the report: http://www.jnsa.org/result/2007/pol/incident/index.html http://www.jnsa.org/result/2007/pol/incident/index.html )
• lacker 18y ago
  The kind of bug big companies are concerned about is the kind that causes google.com to be down for 15 minutes. That's a significant amount of revenue. Or the sort of bug that causes a release of an infrastructure component to be rolled back, causing more work for every project touched by that release. It isn't the famous sort of bug, these don't get picked up by the news, it's the sort of bug that nobody really notices but costs the organization a lot of money or work.