The quickest way to contextualize this article is that it’s like asking crypto true believers to write about crypto a few years ago, just as it was becoming mainstream. Of course someone said there were no real problems on the internet.
1,280 karma · joined December 15, 2014
The quickest way to contextualize this article is that it’s like asking crypto true believers to write about crypto a few years ago, just as it was becoming mainstream. Of course someone said there were no real problems on the internet.
More specifically, if you have a bunch of bugs related to storing data in an inconvenient way, convert the data to a simpler format rather than write a bunch of complex logic around the bad data format.
Article here: https://docs.microsoft.com/en-us/archive/blogs/ericlippert/b...
As a tangent, this article took me ages to find, even though I remembered the author, most of the details, and the string "SensibleDate". I'm not sure if the lesson is that MS is at fault for moving old content and having a lousy internal search tool, or Google is getting worse because it couldn't find it anyway, or I've gotten worse at finding stuff. But a few years ago I would've been shocked to not quickly find an article where I remembered a few relevant details, and now it seems like the norm.
https://web.archive.org/web/20051207043012/http://reddit.com...
Not wearing mixed fibers was never a practical rule, but part of a common theme in Judaism of separating things, like separating milk and meat. Most importantly, the sacred is separated from the mundane, and the Sabbath is separated from work days.
There are quite a few rules in Leviticus that are impressively practical for an ancient people with a primitive understanding of biology: there are restrictions on a touching corpses or people with skin diseases, and frequent handwashing is mandated, including before eating, after urinating or defecating, and after visiting a graveyard.
https://generalaviationnews.com/2011/05/09/fliers-or-liars/#....
Using multiple logically inconsistent defenses is generally allowed in the US.
https://blogs.cfainstitute.org/investor/2021/07/19/myth-bust...
Firing also requires a fair amount of person-hours to do, and if you fire someone and need to replace them those costs stack.
In what sense?
> The rightful owner cannot just steal it back.
The rightful owner doesn't get any special rights, so they can't trespass to get their property back. A policeman could get it back for them, though. If it's just lying there they can take it back themselves. I've heard stories where people find their stolen property on Craigslist, meet with the thief, and steal it back without using force. That's fine.
> Similarly if it wasn't yours, you wouldn't have to pay taxes on it
Ownership is a tricky concept. There are many rights and responsibilities associated with ownership. Owning a bike carries a different set of rights and responsibilities from owning a house. Paying taxes on something is an obligation typically associated with ownership, but since stealing something does not create many of the other legal rights associated with ownership I don't think it's sufficient to say that it demonstrates that it's "yours." Also, of course, no one actually pays the taxes.
If this is meant to be a representative sample of the US, the data doesn't pass the sniff test. They don't provide enough context to understand how else we should understand it.
This post shows an average in every region more than double that. It's not a representative sample. The charts are pretty but I don't think this analysis has any value.
Yiddish has good examples where words actually do not translate easily. EG, schmendrick and schmuck both translate as "a fool", but have distinct shades of meaning that aren't trivially explained. "Nu" is an interjection that has several specific meanings that require long examples to explain, EG: https://forward.com/culture/12736/just-say-nu-01335/
If you like that kind of stuff I highly recommend The Joys Of Yiddish https://www.amazon.com/Joys-Yiddish-Leo-Rosten-1968-06-23/dp...
https://www.securityweek.com/credential-stuffing-successful-...
The term "credential stuffing" is a bit counterintuitive for me as well, but I guess it fits the pattern of credential attacks. "Password reuse" has other meanings, so would be less precise as a technical term.
https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...
The flip side is when I've spent 30 minutes QAing an issue and another 30 minutes writing up what I've learned, and then the response is "I brought that server down for maintenance, it'll be back in a few."
After a few times of that the sys admin is going to get some very poorly thought out bug reports from me, because I don't want to burn any more of my time QAing known issues.
Also, you have to be fairly big to get that kind of leverage. $100 million is probably too small but $1B might be enough.
So you put up $1B of your own money, and a bank would let you go long $3B and short $3B. The idea is that your longs hedge your shorts well so you can't lose too much.
Obviously, in the case of Archegos the shorts didn't hedge the longs well.
So raising a kid who's middle or upper class is actually quite expensive, and that's part of why low income and high income families have more kids than middle income families. https://qz.com/1125805/the-reason-the-richest-women-in-the-u...
If Company X is worth $60B on Monday and $40B on Tuesday then some people who were short could make a lot of money, but in general $20B of value has been destroyed and the world is poorer on Tuesday.
Probably more common is an experience I was in- we found a good candidate, he wanted to finish other interviews before making a decision and I gave him a few weeks to decide, then later I regretted giving him so much time. It meant I had to either pause the candidate search for a few weeks or potentially waste my time and candidates' time interviewing people when there may not be an opening.
The Wikipedia page on "bear raid" mentions a single example, from 1609. https://en.wikipedia.org/wiki/Bear_raid
I still think it's a good idea to allocate some resources towards mitigating low probability, high impact events.