Captain's Log

You made it. There were a dozen moments where you could have stopped. When the terminal threw an error you didn't understand. When a merge conflict looked like hieroglyphics. When the deploy failed at midnight, and the logs were a wall of red. You didn't stop. You're here.

Look astern. In chapter one, you opened a terminal for the first time. Git wasn't installed. A repository meant a library. Deployment was something other people did. Since then, you've pair programmed with an A I agent, shipped a product to a live server, tested it for vulnerabilities, automated a pipeline, and read a security report that agents wrote for you.

Somewhere between your first commit and your first deploy, something shifted. You stopped being someone who uses software, and became someone who makes it. You learned to think in systems, to describe your intent clearly, and to verify what comes back. That shift doesn't reverse.

Now name the planks of the ship you built. The terminal is your helm. Git and GitHub, your logbook and your harbour. The agents are your crew: you brief them, ask for a plan, constrain them with permissions, and read what they hand back, because they're powerful and fallible in equal measure. Deployment gave you sea legs. Security awareness is your lookout. And the review habit is your compass: never ship what you haven't read.

One last exercise turns the book around. Write your captain's orders: an agents dot M D file in the root of your project. What it is. How to build and test it. The conventions, the boundaries, the traps. Claude's own file becomes a one line pointer to it. Keep it to a page, and never put secrets in it. In chapter one, you followed instructions someone else wrote. In chapter ten, you write them.

Then test it. Start a fresh session, give it a real task, and read the diff. When the agent gets something wrong, don't just correct it in the chat. A correction in the chat lasts one session. A correction in the file lasts every session after it. And a rule that must never be broken becomes a deny rule, or a hook.

Your final assignment comes from you. Within seven days, build and deploy one small thing that didn't exist before. The only rule: it has to be live, with an address someone can visit. Then help the next reader, who's opening a terminal for the first time. You're no longer a passenger. You're part of the crew.

The chapters end here. The voyage doesn't. Every project from now on is a new heading on open water, with a ship you built, and a crew you know how to command. Go build something.