The class logbook
The Latest
Everything published on the site, day by day, newest first: guides, analysis, essays and quick thoughts in one running log. The shelves for browsing are elsewhere; this is where you see what is new.
The log
Entries 41–51 of 51
1 entry
1 entry
Give the Agent a Precise Source to Inspect
You know which authentication helper handles the failing request. Give the agent its path and the failing case instead of asking it to rediscover both.Quick thoughtclaude-codecontext1 entry
Separate Permission Decisions From Execution Boundaries
Repeated permission prompts can become a reflex. Automating some of those decisions may reduce interruption, but it also changes which actions proceed without…Quick thoughtclaude-codesecurity1 entry
Turn Repeated Setup Advice Into Maintained Instructions
Your notebook has become a small application, and every new session needs the same explanation: where the tests live, how to run them and which generated…Quick thoughtclaude-codesetup1 entry
Plan When the Approach or Consequences Are Unclear
A one-line change can alter authorization for every user. A hundred-line generated update can be routine.Quick thoughtclaude-codepractice1 entry
Keep a Side Question Out of the Main Thread
You are packaging an application and want to know what --frozen-lockfile means before running the install.Quick thoughtclaude-codecontext1 entry
Separate Shared Instructions From Local Context
Your team needs the test command and branch convention. It does not need your scratch-directory preference in its shared instructions.Quick thoughtclaude-codesetup1 entry
Keep a Session Focused, and Check Its Working Tree
A billing refactor and an onboarding fix have different requirements. Giving each a named session can make their decisions easier to follow than mixing both…Quick thoughtclaude-codepractice1 entry
Pass the Evidence Without the Clipboard Handoff
When an integration fails, the exact error is more useful than your recollection of it. cat error.log | claude passes a file into the CLI without copying from…Quick thoughtclaude-codepractice1 entry
Choose an SDK When You Need to Own the Runtime
A shell command starts your prototype. A scheduled service also needs lifecycle control, credentials, error handling and a way to inspect what happened after…Quick thoughtclaude-codepractice1 entry
Check What the Review Command Actually Runs
Before building a review workflow, inspect the commands and plugins available in your installation. A command named /code-review may come from an installed…Quick thoughtclaude-codeverificationThat is the first entry in the log.
To browse rather than follow: topics, all articles and all thoughts. To learn in order: courses and the book.
