Skip to content
Field Guides

What this site is

Field Guides is a collection of hands-on how-to guides for engineering work: toolchains, kernels, libraries, and systems you actually run. Every guide is built around the same promise:

Commands you can run, versions you can trust, and an honest status on every page.

Who it is for

Section titled “Who it is for”

Engineers who want working knowledge, not marketing. Each guide assumes a specific audience and environment, stated up front on the overview page — so you can tell in one glance whether a guide applies to your setup before you copy anything.

The status system

Section titled “The status system”

Every page carries one of three statuses, and the site shows it on the page itself when it isn’t the good one:

  • verified — every command on the page was executed in the stated targetEnv, and the output shown is real output from that run.
  • untested — parts of the page were not executed (no GPU, a paid API, a cluster you don’t have). The page says which parts and why. The banner “Not executed on hardware — verify before relying on this” is a warning, not a failure of the guide.
  • draft — placeholder or work in progress. Read it for shape, not for truth.

A guide labelled verified that segfaults on your machine is a bug worth reporting. A guide labelled untested that works is a normal Tuesday.

The 60-second check

Section titled “The 60-second check”

Open this site, press / (or Ctrl+K), and search for a word from any guide’s body — for example status. You should get results within a second or two. If search returns nothing, the index hasn’t been built after the last deploy; check back shortly after a deploy or report it.

What’s next

Section titled “What’s next”