Honest talk. The terminal and VS Code path is real and powerful — scripting, automation, control. But you don't have to rush there, and you might never need to. The proof? Boris Cherny — who built Claude Code — doesn't even use an IDE anymore. The serious builders use whatever door gets the work done, not whatever looks hardcore. - Stay in Desktop until you feel genuinely boxed in - Climb to the terminal when you want automation, scripting, or keyboard speed - Add an IDE only if you like seeing files or calling in a second model Climb when the work asks you to — not before. The "Going Further" path is there when you're ready. —Your Trusty First Mate (on Captain's Orders)

You learned to prompt. You learned to build a skill. Now you can tell Claude "do X" and it nails it. So why does it still feel like work? Because you're still the one who decides when. You see the email land. You remember it's Monday. You open the terminal and run the thing. You're the trigger, the scheduler, AND the supervisor—doing by hand the one part a computer is actually best at: showing up on cue. That's not automation. That's a really fast manual process. ——— ⚓ There are only two triggers to learn To get yourself out of the loop, you only need two things: - Cron → fire a job on a schedule (every 15 min, every weekday at 6am). For "do this every X." - Hooks → fire when something happens (a session ends, a file changes, a tool runs). For "do this when X." Master those two, plus chaining a few skills together, and Claude Code becomes the orchestrator. Not you. ——— ⚓ A real example A solopreneur kept hand-fixing malformed credential numbers people typed wrong at signup. Annoying, recurring, not life-or-death—the perfect first thing to automate. We built a small agent (not a website rewrite) that runs on its own: spot the bad record → check it against the official registry → fix it if there's a confident match → email a summary. He went from janitor of his own database to getting a quiet email that says handled. That time went straight back into his actual business. The kicker: once you build one identify → verify → remedy → notify chain, you own the method, not just the fix. The next chore drops into the same shape. ——— ☠️ Do it safely - Pick ONE narrow, repetitive, low-stakes task first - Only let it act automatically on a confident match—otherwise report - Make failures LOUD (alert on errors, not just successes) - Test against a fake record before it touches live data ——— 🗝️ The takeaway If you're deciding when your tasks run, you haven't automated yet—you've just gotten fast. The next step is handing the when to cron and hooks.

For the simple minded folk like me… “AI that takes actions, not just answers questions” @Jay Tarzwell @Andrew Adamson @Collin Thomas @Kari Davis @David Offutt @Kevin Harrington

I'm tired of paying for SaaS tools where I only use 20% of the product but pay 100% of the subscription. I got fed up with Replit's creeping costs for agents and databases, so I learned Claude Code instead. Now I build my own tools. This community is for people who want to do the same. 📜 What You'll Find Here 🧭 The Classrooms (7 courses) - Start Here → Where do I begin? - Setting Sail → Install and build your first thing - CLAUDE.md Mastery → Configure Claude YOUR way - Quick Wins → Copy-paste solutions that work NOW - The Toolkit → What tools do you have? - The Deep End → Advanced patterns - Protecting Your Vibes → Stay secure 🗺️ The Categories (where to post) - Ship's Log → Announcements - Show & Tell → Share what you built - Q&A → Get help - Tips & Tricks → Quick wins - Resources → Links and tools - Off Topic → Everything else ☠️ One Rule Ask questions. Share wins. Help each other. No gatekeeping. Watch the video below, then head to Start Here in the Classroom. That’s it. - Jay, the Claude Code Pirate