At this point, the best way to keep their credibility from further deteriorating is to provide good reports on what is going on. E.g., not like PSN, more like Amazon. Currently that Azure dashboard doesn't even load for me... has it been slashdotted or something?
As an aside: whenever a cloud system goes down, people come out to rag on the reliability of the cloud. While I'm also annoyed by the marketing guys throwing around "just put it in the cloud!!" as much as anyone else, and agree some applications make no sense living in the cloud, I'd also like to point out that for some people, doing the admin work in-house results in the same amount or more headaches.
The prevailing trend in Canada seems to be drifting way from scientific research: http://www.bbc.co.uk/news/science-environment-16861468
Each time I read a new article about my country, I become more and more ashamed to be Canadian...
Not sure how prevalent it is in the U.S., but in Ontario, Canada, "Software Engineering" is recognized as an official type of "Engineer" -- http://www.peo.on.ca/enforcement/Software_engineering_page.html. In Ontario, like the states that you mentioned, it is illegal to call yourself an engineer without being granted the title by the self-regulating engineering body of the province. In order to be granted the title you have to taken part in an engineering university program that's been accredited by that body, and then take some further ethics tests, and work for a while under an engineer who has x years of experience.
It is a fairly new 'discipline' in engineering and I went to such a "Software Engineering" program that is accredited. The thing is, I know zero people in my graduating class of about 90 who actually took the extra steps to become a professional engineer. Mainly for two reasons; a) It only has a meaning in Ontario, and most of the lucrative software 'engineering' jobs are not in Ontario, and b) Even in Ontario, its relevance for employment is fairly limited... approaching useless I would say.
Yeah, f that noise.
Leica M9 or go home.
Wait, I don't see how the security beach at Comodo rules out #1. Maybe I'm not understanding CAs correctly, but the two situations have a big distinction. In the Comodo case, somebody breached Comodo, a CA authority, and issued new CAs which could be used by a malicious site to claim that they are some other trusted site. In the case of Stuxnet, already-issued CAs for Realtek and JMicron were stolen to sign malicious drivers. CAs that had already signed legitimate drivers in the past. Aren't these two cases a bit different? I'm not saying that the CAs at Realtek and JMicron couldn't have been stolen without real human assets, but how does the Comodo case change anything?
Genetics explains why you look like your father, and if you don't, why you should.