3,462 karma · joined August 16, 2013
hnchat.com:QC6b1eMuHsLMnBE6wPaw
Their key mistake.
The 0.1%-0.2% was just bad science, taking medians over countries with lagging statistics reports.
Where did you find 3.4%? Isn’t that an upper bound?
Monitoring, dashboarding and alerting should leverage other BI-class tooling.
From 2021: “Biological markers of brain injury, neuroinflammation and Alzheimer’s correlate strongly with the presence of neurological symptoms in COVID-19 patients.”
[1] https://aaic.alz.org/releases_2021/covid-19-cognitive-impact...
Look at any cloud provider. They get it right because they employ the best security management systems.
Thing is, if I decide not to do that, the impact on my life is relatively minor. What gives graffiti artists the right to impose their personal predilection unto others?
In other words, given your reasoning, what’s stopping me from playing John Coltrane at 110dBA the whole day and night?
Systems die, data stays.
There have been numerous bugs caused by incorrect code formatting, most notably an SSL security bug from 2014: https://dwheeler.com/essays/apple-goto-fail.html
Another reason for formatting is the “minimal diff” paradigm. If a formatting rule would not be followed, in the next commit hitting this code, the format would also be affected, causing a larger diff than necessary.
There are other reasons for simple format linting, but the reasons above are the most profound.
Lastly, formatting is part of a range of static code analysis tools. Generally, formatting inconsistencies are the easiest to detect and resolve, as opposed to more sophisticated tools.