Claude Code: from zero to professional. Tips, tutorials and deep dive guides from an engineer who uses it 12 hours a day.
Explore the hub →Claude Code first steps: the fundamentals that don't expire
The Claude Code fundamentals that don't expire: install, sessions, context, quota, models, permissions. What you actually need to grasp on day 1.
AI: the joy of missing out on what doesn't matter
You can't keep up with AI, and you shouldn't try. The answer isn't resistance or passive acceptance: go all in, but deep on one thing instead of scattered.
Claude Code Agent View: managing parallel agents without leaving the terminal
I spent months managing many Claude Code agents by hand. Agent View now does it: my terminal-native workflow with Warp and Neovim, and the gaps I patch.
Why Claude gets worse the longer your session runs
Hours into the same session, Claude starts fumbling things it used to nail. It didn't get dumber, and nothing's down. It's your context, and it filled up. The fix is two commands.
Claude Code doesn't just write your code, it explains it
When you land in a repo you didn't write, Claude Code can explain every pattern and decision as it works, instead of just leaving the code done. Even Claude Code's creator recommends it, and you can pin it to the project.
Claude Code /doctor no longer just diagnoses: now it fixes what it finds
`/doctor` used to be the report you ran once something already failed. Now it's a full checkup: it finds what's broken and, above all, the dead weight quietly eating your context, and offers to fix it with your OK.
Your plan B for Claude Code's 529 errors
When your model returns a 529 (Overloaded) mid-task, the request doesn't have to die. Configure a chain of backup models and Claude Code degrades on its own instead of leaving you stuck.
Get only what matters
If I have nothing worth saying, you won't hear from me. When I do, you'll be the first to know. 7,000+ people already trust this.
Unsubscribe at any time.