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.

I was wrong.

Originally published .

I was wrong about workflows. I was wrong about acceptance testing. I was wrong about scripting languages. It’s time to fix that. The next few weeks will begin my quest to change the world and right these wrongs.

  1. Workflows are not ever the right answer unless they can be tested and debugged. If you can not test it you can not validate it. If you cannot validate it you will eventually see code rot.

  2. Business needs should be modeled in testing not just whether a unit of code functions but whether it helps to fill a business need.

  3. Scripting languages are a vital tool in the software developer’s tool kit. You can create clean maintainable applications in the right scripting language. To dismiss dynamic scripting languages as toys is wrong.

Changing the world for the better…

Step one: Continuous Integration and Executable Documentation.

Explore the map · Browse by topic and date