I think the point is supposed to be that "following the practices and procedures that limit their liability" = "doing their due diligence to reduce risk in accordance with their credentialing body".
We generally don't hold people liable for acts of God or random chance failures. For example, malpractice suits generally need to prove that a doctor was intentionally negligent on their responsibility.
Everything in real life has quantifiable risk, and part of why we have governing bodies for many things is because we can improve our processes to reduce the risk.
It's not just following orders :) it's recognizing that the solution to risks isn't to punish the actor but to improve the system.
While I can't speak for Knuth, I have been reflecting on the fact that developing with a modern LLM seems to be an evolution of the concept of Literate Programming that Knuth has long been a proponent of.
What is the rationale behind the assertion that Knuth would be so fundamentally opposed to the use of LLMs in development?
I interpret this comment as talking about prioritization across a broader org. A senior engineer should be able to prioritize inside of their team and adjacent teams. But there is a reason why there are levels of engineer beyond senior - beyond just increased technical judgement, there is increased influence in orgs spanning hundreds or even thousands of engineers.
There is always opportunity for growth in this dimension. For example even the CEO has to build the right skills to convince the board of their priorities.
The article seems to focus too much on the consumer side of the bandwidth equation. I think the real win for Netflix is the aggregate egress bandwidth savings from their DCs. If Netflix can halve their bandwidth (as the article seems to claim) without any appreciable loss in quality, they've just saved substantially in the infrastructure and peering contracts needed to deliver their content. I have no idea how much money Netflix currently spends on bandwidth/CDN, but I'd guess it's certainly in the 100s of millions. I can imagine that Amazon and Apple would be very interested in emulating those savings.
While this is a good idea to prevent folks from brute-forcing their way into your machine, the article is talking about DDoS attacks. If you have 150G pointed at your network the issue isn't going to be your servers. It's going to be congestion at your network links. Your SSH settings and Fail2Ban won't help at all in this case. You'll need something like CloudFlare's DDoS protection to identify and block DDoS requests from ever reaching your network.
EDIT: Oops, just saw that the article does talk about SSH brute-forcing. Your point is quite valid.
Was this in the past week? Because just a few days ago I was experiencing a similar problem. I attempted to access https://rememberthemilk.com and chrome complained about the SSL cert, as I was receiving the cert for their CDN and not for rememberthemilk itself. I couldn't find anyone that could reproduce the issue, but it occurred consistently on my computer regardless of browser. It resolved itself 20 min after I first noticed it, but I'm still really curious as to why it happened in the first place.
A large part of this is that the Second Amendment to the US Constitution explicitly protects people's right to bear arms. This has led to gun-ownership being an important topic to many American citizens, initially by people using to utilize guns (ranch rifles, etc) and then by collectors and other hobbyists.
As for your second question, the difficultly of obtaining a gun in the US varies largely by state. However, it generally is not exceedingly difficult. As an example, here is how purchasing a firearm works in California:
If you don't mind me asking, what country did you move too that has better personal rights? I know that Canada and most of the EU have a worse track record than the US when it comes to this.
IMHO moving out of the US just avoids the problem, instead of solving it. We need to put more support behind advocacy groups like the EFF who's mission statement is to fight against the infringement of personal rights.
MySQL, though written in C++, reads more like C with classes. Even then, a large portion of the code is procedural instead of OO. They are slowly moving towards an OO style, but it will take a while before a reasonable percentage of the code base has been re-written.
How is this "beyond astonishing"? 27 years is minuscule on in a geologic time scale. Climate trends are measured in hundreds and thousands of years, if not more.
I would disagree with this article. Most posts through third-party applications will have a motivation to reach the largest possible audience. This will lead to an excessive amount of public posts. Not only will this defeat the purpose of "circles", it will also flood G+ search with noise. This will destroy much of the usefulness of the network.
In my experience there is a large class of people who lack basic curiosity about how things work. They are content to believe that things just "exist". I haven't done much research into this, but I would be interested in seeing if this is considered more an education problem, or if some people simply don't have the capacity for curiosity.
The title is a bit misleading. The campus is not "for Google", but rather a space for start-ups. Only the building is owned by Google.
On a side note, the bear looks like one of the United Buddy Bears from the original Berlin collection. I'm not entirely sure how they got one, but it's an awesome thing to have around. Clearly it's being put to good use, given the Tardis decorating its arm :)
While I agree that the page by itself is not very useful, it still does give access to two huge sources of data that Google has on you: your Web History, and your Google Dashboard. Obviously it would be more useful if they were integrated into the page, but imho providing a link is sufficient for the moment, as this is the first iteration of the page. I'm sure we will see improvements made over the coming months.
I interpreted as "write on the paper at a 90 degree angle to the lines" (aka not the way you should be doing it). This seems to be a standard rehashing of "going against the grain", advice to be different, to not follow expectations. That's not what I would necessarily call bad advice.
This may not be exactly what you're looking for, but I generally resort back to good old 'git grep / grep' when looking through unfamiliar github projects. running grep from emacs links all the matches to their corresponding files, so you can navigate the results and easily follow the code execution by jumping to each result.
While I don't have any statistics, I do not doubt their claim. CloudFlare is a CDN, and as such will handle an enormous amount of traffic. As an example of this, Akamai, a large CDN, handles approximately 20% of the total traffic on the internet. In fact, many sites, such as Wikipedia, Twitter, even Amazon and Google, actually host static content through Akamai. All this content adds up to significant amounts of traffic.
We generally don't hold people liable for acts of God or random chance failures. For example, malpractice suits generally need to prove that a doctor was intentionally negligent on their responsibility.
Everything in real life has quantifiable risk, and part of why we have governing bodies for many things is because we can improve our processes to reduce the risk.
It's not just following orders :) it's recognizing that the solution to risks isn't to punish the actor but to improve the system.