6 thoughts filed under this tag.
It gets it wrong. You correct it. Still wrong. You correct again, and the third attempt is, more often than not, somehow worse. That's not a fixed law, just a pattern I keep seeing: every failed attempt stays in the…
Three hundred lines of instructions and it still breaks your conventions. So you add more rules. It gets worse. Here's my read on why: bloated instruction files cause the model to ignore the instructions that matter…
You ask how the auth layer handles token refresh. It reads forty files into your main conversation, and now the actual implementation runs on a stuffed context, exactly when you need it sharpest. Ask for a subagent…
A long session auto-compacts, the tool that condenses your conversation history so it fits in context again, and suddenly it has forgotten which files you modified and what the test command was. Most people only know…
"The auth helper, I think it's somewhere in src/utils, it handles tokens": and now it's grepping around, burning context to find something you already know the location of. Reference it directly with an @ path and it…
Mid-task you wonder what a flag does. Asking pollutes the session with a tangent that stays in context for the rest of the day. So you don't ask. Which is worse. Claude Code has a slash command for exactly this: /btw…
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.
