2 thoughts filed under this tag.
Before applying a mechanical change across a repository, prove it on a file whose intended result you can inspect completely. Create an isolated worktree and choose a small example with one normal case and one…
A useful bug report contains an input that fails and the result you expected. That gives Claude Code something firmer than “the report looks wrong.” Suppose a weekly summary counts the same invoice twice. Build a tiny…
Learn
Save your progress with a free account.
Checking sign-in…
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.
