4 entries and 9 thoughts filed under this tag.
PracticeClone it, install it editable, run the offline example, then read the 67-symbol API you'd actually build on. A working agent in about fifteen minutes, no API key required.
Rod Rivera
Install a real open-source framework, subclass one class, and run it. Then break it on purpose two different ways, because a tool you have not watched fail is a tool you do not understand yet.
Install the zeo CLI, write a real Statement of Work, and hit the exact schema error a beginner hits first. This is the tool this site's own governance arguments run on.
Every business has one: the customer list that lives half in a spreadsheet, half in an inbox, and half in someone's head. Here is how to clean it in about twenty minutes, and — the part nobody teaches — how to prove the cleaning did not quietly drop forty rows.
You won't let it attempt the aggressive refactor, so you micromanage every step and get a worse result slowly. Every prompt creates a checkpoint. Double-tap Escape, or run rewind, and restore the conversation, the code…
A pattern worth watching for: you write a long spec, it builds the thing, and you discover at the demo that you never thought about the edge cases. Flip it. Start with almost nothing: "I want to build X. Interview me in…
For a change that touches two hundred files, don't run one enormous session. Generate the task list to a file, then loop the agent over it one file at a time in headless mode. The part that makes it safer is the…
You've caught yourself typing "and don't forget to run the linter" for the fourth time this week. That's the tell. Most people treat skills as documents the model reads when relevant, but they can be workflows that take…
Say you're refactoring the billing module and also fixing an unrelated UI bug. Those two jobs have nothing to say to each other, they just need to not overwrite each other's files. That's not a job for agent teams…
You ask for a feature. It starts editing immediately, and solves the wrong problem in the wrong place. Plan mode separates exploration from implementation. First: read this directory and understand how sessions work…
You start on the billing refactor, get pulled into the onboarding flow mid-afternoon, and never leave. One session now carries both, plus whatever else came up. By evening the output on either has quietly gotten worse…
cat error.log | claude: the log goes straight in, no copy-paste, no truncation, no mangled formatting. Prefix a message with ! and the shell command runs with its output landing in context, which is faster than…
You're writing shell loops around the Claude Code CLI to build a Slack bot, or a pull-request reviewer for CI, or a pipeline that fires on a schedule. That's the point where you've stopped using the tool and started…
Cookie duty
The one he did not eat is a measurement cookie. Say yes and the site loads Google Analytics (GA4), which stores an identifier in your browser and lets us count which lessons get read.
Change your mind any time with Privacy choices in the footer. Read the Privacy Policy
Optional · newsletter
That is saved and settled. Separately, and this is marketing rather than measurement: Rod writes a weekly email — one lesson, one field note — sent through Kit. It has nothing to do with cookies, and skipping it costs you nothing.
We will send a confirmation email. Click the link in it and the next lesson finds you.
