extremes

Knowing extremes and layout boundary conditions: You can reasonably test extremes of wide and condensed font metrics; it's not that hard.

To take two extremes, if you're working on creating CSS templates for a Django website, stay in school.

Besides testing artificial extremes of wide and condensed font metrics, practical testing across multiple environments isn't anything new.

With some other traits the differences are small on average but can be large at the extremes.

These extremes cover about 10% of any org, max, and the rest are all completely unserved by the process.

Nevertheless, it is not actually necessary to go to extremes (see fallacy of excluded middle).

Our desire for simplicity will lead us variously towards either of these extremes, and our experience tells us how to tread.

You are agreeing that autonomous <-> executive are two extremes of a spectrum, no?

But to be honest people are taking their specification and dooms-day-ism to stupid extremes.

At the extremes of this path friction slows everything down to a crawl.

Historically, both extremes become militaristic and convinced of a duty to righteous aggression.

That's because you treat VR vs AR vs reality as three different extremes.

The majority of users probably don't care either way, so we're only talking about the two extremes - and I'd hazard a guess that there are far more people who would rather Github didn't have an "anything goes" policy than did.

The story "I Have No Mouth, And I Must Scream" is about two computer systems set on opposite sides of a war, and driven to extremes until one of them became self-aware, the birth of AI, and ate the other computer system.