pavement

Hmmm, a dearth of activity on an article about employers expending significant effort, prying into extracurricular social media activity.

Maybe this article just "isn't very interesting" and suddenly there are better things to discuss elsewhere.

Holy shit. That is not even a "pull down menu" as previously reported.

Good to know. This means that in Hawaii, you should only think about taking action if the magic FALSE ALARM notice never appears.

If the FALSE ALARM notice doesn't appear within an hour, it might just be that the false alarm guy is on lunch break. If it doesn't appear in 8 hours, it might mean that a shift change occurred without proper hand-off. If it fails to appear in 24 hours, a nuclear attack might actually be imminent, and you should check other sources, to determine if the alarm was, in fact, real.

This protocol ensures that archaeologists will receive a valid record, omitting the false alarm notice in the rocks on the other side. Eventual consistency ensures that before the archaeological record is written, a false alarm notice will appear, if the alarm was indeed false. In all other cases, the alarm is effectively revealed to history to be a true alert, at some point in the future, as yet to be determined.

I disagree.

Gross. It sounds like a total failure to correctly model reality.

Like measuring how blue the sky is, based on how much "blue" is left in the universe. The idea they attempt to quantify is improperly described in terms of qualities. e.g. Do colors even work that way?

(...and keep your planck unit, M theory, quantum field eigenstate, history-of-the-big-bang, age of the universe remarks away from this hypothetical example, please. You know what I mean when I describe the sky as either blue or not blue in the colloquial sense.)

That Napster is depicted as a footnote is pretty inaccurate, considering the title. Paint his story as the story of a kingpin, but this is not "the dawn of" anything beyond his personal tale.

wtf am i readin

Except... the very premise of the service isn’t particularly reasonable.

You won’t change my mind, so don’t bother replying.

And this is why I don’t pay for a Netflix subscription.

What is it with engineers willing to brainwash themselves regarding what constitutes a “good compromise” within the context of what their paycheck depends on?

An infinite spacefiller that produces a flood of wikipedias in a simulation will simply trigger out-of-memory exceptions, silly.

Likely, employers and what is possible in the immediate day-to-day sense.

Payment processors frequently conduct "no-capture" test transactions for authorizations of possibly $1, before tokenizing CC info. Arguably, this follows the pattern of an integration test.

Ecommerce providers often follow a process of cycling an immaterial test product through a real credit card for pennies, with a petty cash credit card, to exercise the purchase/refund cycle, end-to-end, depending on the activities of the project. A runaway batch process with an infinite loop of purchases is bad, infinite refunds is even worse.

Sometimes these tests are needed to ensure that the service account exists on the third party system, is recognized, and has limited permissions for a fixed, restricted set of API calls. The tests might be run only during a release deployment, against live production, but more frequently against a third party sandbox host while coding. This is a very common pattern.