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 21–40 of 51
1 entry
1 entry
Test the Build Your Customer Will Receive
A development server passing its tests does not establish that a production bundle behaves the same way.Quick thoughtclaude-codeverification1 entry
Trace One Failed Request Through the Logs
A page can fail after three services have each logged something that looks successful. Start with one request identifier, not the loudest error message.Quick thoughtclaude-codedebugging1 entry
Preview Every Rename Before Moving Files
Renaming two hundred client documents is easy to request and surprisingly hard to undo when two names collapse into one.Quick thoughtclaude-codefile-operations1 entry
Give Claude a Broken Example Before a Fix
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…Quick thoughtclaude-codetesting1 entry
Give the Agent an Inspectable Check
You ask if it's done. It says yes. You check, and it isn't. A completion claim needs evidence you can inspect.Quick thoughtclaude-codeverification1 entry
After Repeated Corrections, Rebuild the Task Context
The agent repeats the wrong approach after two corrections. My rule of thumb is to stop adding conversational patches and restate the task from the evidence.Quick thoughtclaude-codecontext1 entry
Test Whether a Shorter CLAUDE.md Helps
Three hundred lines of instructions and it still breaks your conventions. So you add more rules. It gets worse.Quick thoughtclaude-codecontext1 entry
Delegate Discovery With an Evidence Handoff
An authentication investigation can touch dozens of files before identifying the two interfaces that matter.Quick thoughtclaude-codecontext1 entry
Know What Rewind Can Restore
Before a refactor, decide what you would need to restore. Claude Code's rewind can recover tracked edits and conversation state; it cannot undo every effect…Quick thoughtclaude-codepractice1 entry
Use an Interview to Expose Gaps in the Brief
The stakeholder asks for a useful assistant. Before choosing a framework, find out which result they would accept and which mistake they cannot tolerate.Quick thoughtclaude-codepractice1 entry
Put Repeatable Checks in Command Hooks
Your acceptance criteria say the linter must run after an edit. Putting that sentence in the agent's instructions still leaves execution to the model.Quick thoughtclaude-codeverification1 entry
Make Completion Checks Explicit, and Test Their Limits
The session says the feature is complete, but the build is red. A defined completion check gives you better evidence than that summary.Quick thoughtclaude-codeverification1 entry
Give the Reviewer a Fresh View of the Change
The session that wrote your rate limiter has already seen the argument for its design. For a useful second look, give a fresh session the diff, acceptance…Quick thoughtclaude-codeverification1 entry
Triage Review Findings Against the Requirement
A review returns twelve plausible findings. Fixing all twelve can add more complexity than the original feature, especially when some describe states the…Quick thoughtclaude-codeverification1 entry
Bound Each Run Before Scaling a Migration
A migration across two hundred files needs a task inventory and a way to check every result. One headless run per bounded change can make failures easier to…Quick thoughtclaude-codepractice1 entry
Parameterize the Brief, Verify the Execution
You keep asking for the same issue workflow: read the requirements, locate the change, implement it and run the relevant checks.Quick thoughtclaude-codepractice1 entry
Keep the Handoff Outside the Summary
After a long debugging session, the next turn remembers the proposed fix but loses the failing input.Quick thoughtclaude-codecontext1 entry
Separate the Checkouts, Then Integrate the Work
You want to refactor billing while fixing an unrelated UI problem. Separate Git worktrees give the two tasks different working directories and branches, so…Quick thoughtclaude-codepractice1 entry
Test What a Different Model Adds to Review
A second model can give you another view of a migration or payment change. That is useful only if its findings survive inspection.Quick thoughtclaude-codeverificationContinued on the next page.
To browse rather than follow: topics, all articles and all thoughts. To learn in order: courses and the book.
