FIELD NOTES

The details behind the tools.

Worked examples, practical tradeoffs, and useful limits. Read before you ship.

How much randomness does an API key need?

Start with random bytes, then choose an encoding. Length and entropy are related, but they are not interchangeable.

Readable claims are a debugging aid. They are not evidence of identity, permission or a valid signature.

The same five fields can describe different instants. Check both the expression and the scheduler’s clock rules.

Inventory resource origins, start with observations, then enforce a policy your application can actually satisfy.

Schema inference gets a draft started. Business constraints need evidence beyond one example.

Generate records offline, inventory your senders, and measure alignment before enforcing DMARC.

Compose a portable HTML fragment while keeping local images and drafts on your device.

Randomness, ordering and compactness solve different problems. Select them deliberately.

A useful mock dataset should reproduce a bug without importing a real person’s information.

Combine build patterns carefully and remember that ignoring a file does not remove its history.