Because we've somehow as a culture made the decision that violence is to be glorified, but sex and bodies are still shameful — except, apparently, when we use them to sell things, and even then we can only be suggestive, not explicit.
That reminds me of something that happened at the movie theater when I went to see Hunger Games. There was a couple with a small child maybe 5 years old. They asked what Hunger Games was about and the employee said it was about a bunch of teenagers brutally killing each other for sport. The father, without flinching, said "as long as there's no sex we'll take 2 adults and one child ticket!"
Your database is just about the worst place in the world to be strict about DRY. It turns out, your model and validations don't actually prevent broken data. They just make you think you're safe from it...
...until your broken data starts biting you and your customers in places that don't typically see sunlight.
I'm reminded of the 'cstross quip, "Libertarianism is like Leninism: a fascinating, internally consistent political theory with some good underlying points that, regrettably, makes prescriptions about how to run human society that can only work if we replace real messy human beings with frictionless spherical humanoids of uniform density."
Wrong. All it takes is a browser fingerprint. If they can associate that with a name, whether or not you're logged into the porn site — e.g., through sites that you are logged into — they can identify your browsing session on the former.
"Web browsers leave an essentially unique footprint every time you visit a web page, even in Incognito mode (and even without supercookies). This is well established; many web tools such as Panopticlick will confirm that you give a website lots of information about your computer every time you visit."
...especially if he can put that he's gotten that big a payout from Facebook's bug bounty program on his résumé.
This isn't (generally) about the absolute dollar amount. It's a prestige thing, it's a pride thing, and it's an accomplishment thing. For the preponderance of people that participate in bug bounties, the money is probably very much secondary.
Yeah, you absolutely can't trust client-generated timestamps. We have a table tracking metadata on customer-uploaded photos (dimensions, file size, color profile, &c), including the camera's timestamp. According to their cameras, our customers have uploaded pics taken before the Buddha sat beneath the Bodhi tree, and after the Khitomer Accord was signed.
Fortunately, we also store an upload timestamp, and our servers all sync to local NTP.
What's really funny about this comment is that, while all of the features discussed in TFA are fully standards-compliant SQL, MySQL implements none of them, and its "upsert" isn't.
EDIT: And before one slags PostgreSQL too hard for not currently supporting upsert, one might peruse the relevant pg wiki page  to better understand where development stands and why we don't yet have it. (Hint: it's actually kinda complicated, assuming you want it done, you know, "right".)
Both MySQL and SQLite's implementations work satisfactorily, so I tend to think that PostgreSQL's reluctance is the perfect being the enemy of good.
It's a pattern that shows up often when you're mirroring data from a third-party, so it's a shame that the programmer has to do conflict handling for an operation that the database could easily do atomically.
"Get right" probably isn't the right term. Mostly I'm just annoyed that I can't choose an open source DB that has upsert (or merge if you want to do the standards version) and CTEs. I generally have uses for both of these in every project I work on.