Oddly, the original publication calls out the use of Google Inception v4 CNN in the Methods, but the CBS News article doesn't mention it at all.

They didn't fire everyone because of automation. They fired everyone because the business was grossly inefficient and bankrupt, and it happened over several years. They automated because it was the only way to compete in their market and survive as a company.

Bob Beck has a pretty healthy track record of throwing verbal grenades with regards (but not limited) to open source licenses, security, and other people's code.

That said, looking at published vulnerabilities (CVEdetails.com), OpenSSH and OpenBSD have a tremendous record for fixing (or simply not having) serious security bugs. The total number of vulnerabilities in OpenSSH (application) since 1999 is 61 (11 being DOS) and NONE have known exploits. OpenBSD (an entire OS) has 136 (57 being DOS) since 1999 with 4 known exploits.

By Comparison, OpenSSL (a protocol library) has 87 (46 are DOS) with 5 known exploits.

None of these are egregious compared to other UNIX OS platforms like AIX (316), Solaris (533), and HPUX (278).

I don't think the OpenSSL folks are bad, but they let the product stagnate a bit. Getting some new perspective on it is a good thing.

Wherefore art thou Dennis Ritchie?

I've never really had the time or inclination to be a BOFH, but you can't block any fantasy football sites because even managers "need" them.

I once had an issue with a woman that used to go to gambling sites at work. When we blocked them, she complained to her boss. I was amazed that her boss had the balls to ask us to allow it... but he was the CEO's brother.

I have witnessed BOFH-type abuse by a consultant against another IT person. The guys did not get along, so the consultant blocked all the sites that other guy went to, and when confronted about it, he pretty much said, "F-off. I am in charge of the proxy". Hardocp is the only one that comes to mind. It got so bad that one of the networking guys built another proxy server "for testing" and gave the IT folks access to it.

We fired the consultant about a month after I found out what he was doing.

I worked at a small software firm where the DBAs and programmers were one and the same. The problem came about when one of the owners decided that IT should report into the head DBA/Programmer. Unmitigated disaster. The head DBA truly believed that he understood servers and networks because he had written code that ran on them. It lasted about 3 weeks.

The crazy part was when they tried the same thing a few years later. It lasted about 6 weeks