To the extent that is true, I agree, they should see the positive impact of what they do as well. Your blind faith in the regulatory regime, however, is deeply undeserved. Many approved drugs prove to be dangerous and we can reasonably expect that many effective drugs never make it to market because of bureaucracy.
I understand some people are checking boxes, with no space to consider their impact. Please generously reinterpret my point to extend to their management stack and the political establishment that is responsible for the system.
Those who establish, support and tolerate that system should be as directly exposed to its consequences as practicable. It is good for them to see these stories and feel the consequences of their decisions.
Regulators are, in general, too sheltered and disconnected from the impact of their actions.
Incentives matter. When you get to make decisions that impact others, but not feel any of the costs associated with that, you do not have the correct incentives. I hope the staff of FDA read this and can’t sleep tonight. We can hope they feel some emotional pain, even if it is only some small subset of the pain they have and continue to cause to others.
Counting lines of code, commits, changesets or any other simple metric will destroy your culture.
The team _will_ find out, and then instead of contributing to the success of the business in earnest, they’ll be doing stupid things like maximizing their changesets or racing for “easy” large changes like deleting a module.
It doesn’t matter whether those values do or do not correlate with reality (IMO, if they do, it is for relatively junior engineers only). If you give off the smell of measuring people like that, you will ruin any collaborative team environment and you risk never being able to recover that.
There’s a good chance you’ll chase away excellent engineers with this sort of low-effort metrics management too.
> Recruiters at my company aren't explicitly told to hit certain quotas, but they are given larger bonuses for diverse hires and they do have targets for certain percentages of diverse candidate.
I'm definitely not a lawyer and I live nowhere near the Bay Area, but by my reading of most of these laws, this is illegal. I realize we often interpret these issues differently depending on who they effect, but this sounds like an open-and-shut case of discrimination to me.
He almost surely means Compilers: Principles, Techniques, and Tools by Alfred V. Aho, Monica S. Lam, Ravi Sethi, and Jeffrey D. Ullman [1]... or one of the earlier versions of the book with different authors and titles ;-).
As was common for 80s software textbooks, this was nicknamed for the distinctive image on the cover.
But (and now your edit clarifies that this indeed was your point), perhaps your point is just how difficult it would be to automatically disambiguate nicknames in diverse communities like StackExchange.
This article doesn't seem to answer the question. It just asserts, without evidence, that "luxury is about no-nonsense boldness." Why wasn't this true in the past?
I went ahead and flagged this. It is not HN quality. It is not even Globe and Mail quality.
The other comments have already expressed why that is the case - but in summary, there is no security flaw coherently expressed here, Excel is possibly the right tool for the job (it saves tens of thousands of dollars of custom software development through government acquisition programs) and the editorialism in the title was unnecessary and further hurt the credibility of the "point."
I am generally against often-called "excessive regulation," but the regulator -- perhaps FTC -- should aggressively prohibit the misleading marketing message here.
The entire problem manifests from calling this lane keeping mechanism "Autopilot." Tesla should be prohibited from using that language until they have achieved a provably safer self-driving level 3+.
The problem is exacerbated by Musk's aggressive marketing-driven language. Saying things like we're two years out from full self-driving (first said in 2015) and the driver was warned to put his hands on the steering wheel (15 minutes prior to the crash) makes Musk look like he is plainly the bad guy and attempting to be misleading.
"Provably safe" probably means some sort of acceptance testing -- a blend of NTSB-operated obstacle course (with regression tests and the like) and real world exposure.
If that is the case, why are there only 2000? The conditions must be more complex than that. Unless 2000 is nearly every phone they touched in that time period?
I'm having a hard time speculating about what phones are "encrypted cellphones" by this count. Are they counting iOS devices with a strong passcode or is there some other functionality they're specifically "having trouble" with? I find it hard to believe they're talking about Phantom and specific-application "cryptophones."
Please write to CIPPIC [0] and the Members of Parliament [1] and Members of the Provincial Leglisation [2] for both your local jurisdiction if appropriate and Halifax, Nova Scotia to help protect this kid. The federal Minister of Justice [3] and Technology [4] may be good additions. Remember what happened last time we let a government go wild on a kid incrementing a number in a public URL.
The fact is, it is the organization who published "personally identifiable information" on the public internet who should be punished - and, in any case, criminal law is not the tool to do it. The kid who incremented a number in a URL to download that information is not the bad guy. What if the kid was not Canadian? Are you going to try to extradite a Russian national over accessing information on a public web server?
When a server announces to the world that it can answer HTTP requests, making a reasonable number of HTTP requests is, to me and most technologists I know, authorization (and thus, should be seen as with colour of right or non-fraudulent). The fact those HTTP requests released data he was apparently not entitled to is a security issue, a bug, a problem to be paid for by the actor who manages the HTTP server, not a problem of law. Unfortunately, this section of law has not been used often enough to clarify to me the interpretation of those words.
Here are some follow on questions:
- Why was there "personal information" in FOI releases? Surely a FOI release was intended for the public, as that is the intent of the act. Who's fault is it that there was undesired information in the releases?
- How do we get this law changed? As the law is written, it hangs on the words "fraudulently and without colour of right" - the rest of the clause is incoherent babble of a 1985 technophobe.
That is a significant amount of money for what has been a handful of people, not taking venture capital, now operating as a nonprofit to "secure communications."