Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

Tautology and the Programmer

Originally published .

I’ve decided to extract and simplify an example of why a programmer should know what a tautology is… I found very nearly exactly this code in production a few years ago:


if(!a && !b) {

  if( ! (a || b) ) {

    // stuff

  }

}

// ... more unrelated stuff

The if inside another if creates an implicit and … further obviated by the fact that there is no else to the inner if statement.

But, what’s worse the inner if is automatically true if the outer if is also true. The nested if statements form a tautology! The result is that a maintenance programmer must read and comprehend that he is looking at a tautology and understand how to edit the code.

What is particularly bad is if the maintenance programmer doesn’t understand that there is a tautology in the nested if statements and is tempted to put an else after the inner if. That nested else will never fire… and the programmer may waste hours or days trying to figure out why.

Explore the map · Browse by topic and date