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–60 of 124 · by original publication date
9 entries
MCP Token Audience Validation: A Worked Denial Case
Validate an MCP token for the receiving service as well as its issuer, expiry and scope. Test wrong-audience denial before protected work executes.12 min readmcpauthorization
Pydantic Strict Validation: Choosing What an Input May Become
Learn Pydantic strict validation to decide which conversions a quantity field should accept, and which ones deserve a clear rejection.12 min readPydanticdata validation
RAG Access Control: Stop Leaks Before the Prompt Builds
RAG access control means filtering by permission before retrieval, not after the answer is written. A worked two-user case shows where checks belong.11 min readRAG access controlretrieval security
Remove Irrelevant Context Before Buying More
A longer context window does not make every document relevant. Extra material can make it harder to see which source supports a decision.Quick thoughtopenaipromptingScheduled publication timezone: the worked case
Why a date-only release rule needs one clock across build, request and cache before a scheduled publication timezone decision is trustworthy.9 min readschedulingtimezones
Stateless MCP Application State: Where Identity Really Lives
Keep MCP job state durable while connections change. Check authenticated identity and job permissions on each protected request before resuming work.10 min readMCPapplication stateUpdated
Translate a Coding Agent Benchmark Into a Release Decision
A coding agent benchmark evaluation measures one task distribution. Learn to check whether it matches your actual release decision.11 min readevaluation engineeringcoding-agents
Write an AI Agent Handoff Checklist That Actually Verifies
Learn to write an AI agent handoff checklist that lets a new engineer verify state and evidence instead of trusting a summary.13 min readAI agent handoff checklistagent memory
1 entry
Give a Reasoning Model a Clear Destination
A difficult task benefits from a clear outcome and constraints. A long prompt full of instructions to “think harder” may add little useful information.Quick thoughtopenaiprompting1 entry
Record the Model Alongside the Prompt
A saved prompt is not a complete experiment record. The model, relevant settings and test inputs can all affect the result.Quick thoughtopenaievaluation1 entry
Write the Evaluation Before Tuning the Prompt
Prompt tuning is hard to assess when the definition of “better” changes after every answer. Freeze a small acceptance set first.Quick thoughtopenaievaluation1 entry
A Valid JSON Object Can Still Be a Wrong Answer
Structured output can make a model response easier to parse. It cannot tell you whether the invoice number or amount was extracted correctly.Quick thoughtopenaistructured-output1 entry
Test a Model on the Exceptions You Actually See
A model can handle ordinary support tickets well and still fail on the exceptions that consume most of your team's time.Quick thoughtopenaievaluation1 entry
Keep a Codex Handoff Smaller Than the Session
A handoff should let someone resume the work without replaying every exploratory turn. Give them the state they need to make the next decision.Quick thoughtcodexworktrees1 entry
Ask Codex to Locate the Source of a Generated File
A generated file can look like the obvious place to fix a typo. The next build may overwrite that edit and bring the problem back.Quick thoughtcodexcode-review1 entry
Turn a Repeated Codex Task Into a Tested Skill
If you paste the same cleanup instructions every week, the reusable asset is the procedure and its examples, not the conversation history.Quick thoughtcodexskills1 entry
Check Codex's Exit Status Before Using Its Output
A command can print plausible output and still fail. Your next automation step should require successful completion and a valid artifact.Quick thoughtcodexautomation1 entry
Use Codex on a Small, Known Migration First
Before applying a mechanical change across a repository, prove it on a file whose intended result you can inspect completely.Quick thoughtcodextesting1 entry
Give a Codex Skill One Example It Must Reject
A skill can look excellent on the example it was written for. A nearby request outside its scope reveals whether its boundary is clear.Quick thoughtcodexskillsContinued on the next page.
To browse rather than follow: topics, all articles and all thoughts. To learn in order: courses and the book.
