workflow

Stop hoping that relevant information will fit in the context window. Start manufacturing a task-specific context file before the task begins. The mechanism, the receipts, and the benchmark that gates it shipping.

Long-running tasks fail silently if the session dies before the result is ready. This is the runner I built to make "email me when done" actually mean that. Retry loop, fallback email paths, and a last-ditch file.

Why the regression models that came out of the hackathon got replaced within weeks by three agentic tools. The short version: probability scores without narrative are not what analysts need.

A file I read at the start of every session, twenty-three numbered patterns of how I have broken my own system, and the pre-flight skill that checks proposed work against them. The pattern is the most portable thing on this site.

A vague ask ("give me a list of prospects that look like X") turned into a working pipeline across three data sources in under sixty minutes. A small build, but the speed is the point.

My seven-year-old had a specific game in mind. Sixty conversational turns later, it was playable on her iPad. A short story about the easiest, most rewarding build I have done.

Running Claude, Gemini and GPT-5.4 on the same question in parallel, blind Round 0, informed from Round 1 onward. What works, what does not, and the confidence trap I did not predict.

The difference between using AI a lot and being AI-native: infrastructure as the binding constraint, not model capability.