Articles
Claude Quiz: 25 questions. One certificate.
Tap through 25 questions on everything so far, see right or wrong with the why, get your score and a reading list, then print a certificate with your name. New here? It doubles as a map of the series.
Start the Claude Quiz
Pick the right model. Spend less. Run in parallel.
Four dials most people never touch: model, effort, context and parallel sessions. Aliases, opusplan, /usage, ten ways to cut tokens and git worktrees, in the terminal and VS Code.
Read Day 12
Run it without you. Keep the guardrails.
Run Claude Code from scripts with claude -p and from GitHub Actions: safe permissions, JSON output, budgets, @claude on issues, automatic PR reviews and scheduled jobs, in the terminal and VS Code.
Read Day 11
One command. A whole setup.
Plugins bundle skills, subagents, hooks and MCP servers into one install. Marketplaces, scopes, vetting a plugin, building your own and sharing it with a team, in the terminal and VS Code.
Read Day 10
Delegate the work. Automate the rules.
Subagents give big jobs to helpers with their own context and tools. Hooks run your rules every time: notifications, auto-format, protected files. What, why and how, in the terminal and VS Code.
Read Day 9
Teach it once. Reuse it forever.
Write and install skills and custom slash commands, with a real working example: what they are, why they help and how to build them, in the terminal and in VS Code.
Read Day 8
Plug it into your real tools.
Connect Claude Code to Sentry, GitHub and your database with MCP: transports, scopes and a shared .mcp.json, permissions for tools, tool search and output limits, and security habits, in the terminal and in VS Code.
Read Day 7
Let it commit. You review.
Use Claude Code with git: start from a clean branch, review changes, write commits, open pull requests with gh, run code reviews and work in parallel with worktrees, in the terminal and in VS Code.
Read Day 6
Keep it sharp. Stay in control.
What fills the context window and how to manage it with /context, /compact and /clear, plus permission modes and allow and deny rules, in the terminal and in VS Code.
Read Day 5
Ask clearly. Plan before you build.
Write prompts that work the first time, use plan mode and the explore, plan, build, verify loop, and learn the commands and shortcuts that keep you in control, in the terminal and in VS Code.
Read Day 4
Set it up once. Use it anywhere.
Install Claude Code in the terminal and in VS Code on Windows, Mac or Linux, with shortcuts, a safe first session, eight tips and fixes for the usual snags.
Read Day 3
Give Claude Code good context
It starts every session knowing nothing about your project. A short CLAUDE.md and clear asks stop the guessing, with a template you can copy.
Read Day 2
Anyone can use Claude Code. Using it well is different.
It works so well out of the box that it's easy to think you're already using it well. Four habits close the gap between "it works" and "I trust it", plus a simple loop to start with today.
Read Day 1What's coming
A new article lands here every day. The order may shift as we go.
Foundations
Using it well
Extending it
Automating it
Check yourself
Going further
Follow along
I post a short version of each article on LinkedIn every day. The full write-up always lands here.