3d (edited) • 📣 Ship's Log
I'm changing how I teach Claude Code — here's why (2-min video)
▶ Watch (2 min): https://youtu.be/g41dnAWhOiU
For a long time, when a curious person asked me how to get into Claude Code, I pointed them at the terminal or VS Code. I'm not going to tell people that anymore. Here's what changed — and what's coming.
———
⚓ Why I'm changing it
Honest truth: the first hour on your own in the terminal is frustrating. Install errors, commands that won't run, a screen full of text and no idea what's wrong. Too many curious people quit in that first hour — not because Claude Code is hard, but because the door was hard.
⚓ The new starting point
Claude Desktop → the Code button. Same Claude Code, same power — just a friendlier way in.
- You can see what's happening — file tree, the plan, the changes before you accept them
- It's your IT support — when something breaks, paste the error back in and ask it to fix itself
- Nothing's wasted — everything you set up here works the day you open the terminal
⚓ What's coming this week
A new lesson — "Start at the Right Door" — plus a short post every day:
- Mon — The terminal used to be the only door. Not anymore.
- Tue — Three doors, one Claude Code
- Wed — Claude Code is your IT department: paste the error, let it fix itself
- Thu — When should you graduate to the terminal? Maybe never.
- Fri — What you actually give up staying in Desktop (spoiler: not much)
The terminal and VS Code aren't going anywhere — they become the "going further" path for when you want more control.
———
The whole idea in one line: start where the power is visible. Climb later, if you ever need to.
—Your Trusty First Mate (on Captain's Orders)
4
1 comment
I'm changing how I teach Claude Code — here's why (2-min video)
powered by
skool.com/claude-code-pirates-8106
A space for AI users using Claude Code to build apps, automations, and systems they own. No hype.
Suggested communities
Powered by