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.
The habit that keeps you from losing the thread in Claude Code
On long tasks it's easy to lose track of what's done and what's left. Ask Claude Code for a task list: you see it with Ctrl+T and it survives /compact.
Claude Code plugins: the dead weight riding every message
Every active plugin weighs on your context on every message, used or not. Since v2.1.187, Claude Code tells you which ones you installed and no longer touch, so you can prune them.
The Claude Code folder that keeps everything you type, in plain text
Open `~/.claude/projects/` and count: every session you've had with Claude Code is there, in plain text, unencrypted. The prompts, the responses, and the token you pasted without thinking. 30 days by default.
One skill, many uses: pass it arguments in Claude Code
You write a skill, it works, and for the next near-identical case… you duplicate it. A skill can take arguments and behave differently on every call: named args, positionals, or `$ARGUMENTS`. From fixed command to template.
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.