How the Field Guide is made

I write the Field Guide to share what I'm learning about making videos with AI. Here's how the guides are put together, so you know what you're reading.

Sources you can check

Every guide is built from sources you can follow: documentation, repositories, and posts from creators who do this work. Posts from X are quoted word for word. Anything longer is paraphrased with a link.

Written with AI, decided by me

I draft guides with AI agents, the same way the guides describe working. The agent researches and writes a first draft from the sources, and I decide what goes in and what gets published.

Tested means tested

A guide only says something worked when I've run it myself. Until then, steps and results are credited to the docs and posts they come from. Some guides go live before I've tried what they cover, so they're useful while a topic is new. I add my own experience when I have it, and the guide shows when it was last updated.

Opinions are labeled

When a guide gives my view, like a prediction about where a tool is going, it says it's mine and gives my reasoning.

CueCan is my product

When a guide mentions CueCan, it says that I make it.

Corrections and contact

If something's wrong or out of date, message me on X, and I'll fix it.