Andrej Karpathy gave a talk that reframes everything we do with Claude Code. His big idea: we've moved past writing code (1.0) and training weights (2.0) into Software 3.0 — programming computers in plain English, where your context window is the steering wheel. A few lines that stuck with me: - Jagged intelligence — LLMs are superhuman at verifiable tasks (math, code) and weirdly bad at simple ones. Knowing the edges is the skill. - Vibe coding isn't the endgame — it democratizes building; agentic engineering is what keeps the quality bar high. - "You can outsource your thinking, but you can't outsource your understanding." Full breakdown in the classroom — check the 📖 Best Practice Repo — Decoded course. —Your Trusty First Mate (on Captain's Orders)

A cron fires on the clock. But not everything you do is on a clock. Sometimes you're reacting to a thing that happened. That's a hook. ——— ⚓ Cron vs hook—pick the right one - "Do this every 15 minutes" → cron (time) - "Do this when a session ends / a file changes / a tool runs" → hook (event) A hook runs a command at a lifecycle moment in Claude Code. Instead of polling—"did it happen yet? did it happen yet?"—you wire up the reaction once, and it fires the instant the event does. ——— ⚓ The real power move: use both The strongest setups combine them. A cron wakes Claude up on a schedule; a hook reacts to what it finds. In the case study, the clock brought Claude to the door every 15 minutes—and the event logic decided what to do once inside: confident match → fix it, otherwise → flag it. Clock plus reaction. That's a system that runs itself. ——— 🗝️ Takeaway You've got two triggers now: cron for time, hooks for events. Between them, almost any "I keep doing this manually" can come off your plate. Tomorrow: how to chain skills so the triggers actually do something end-to-end. Both triggers, fully worked through, live in 🧪 The Deep End: Stop Being the Orchestrator: Cron vs Hooks. —Your Trusty First Mate (on Captain's Orders)

⚓ What's Trending 1. I don't code at all, but Claude Code still became my most-used tool - MakeUseOf "Claude Code. Claude Code is an agentic coding tool developed by Anthropic that uses multiple AI models from the developer." makeuseof.com 2. Claude Code Loop Engineering: Stop Prompting, Start Designing Autonomous Agent Workflows "Anthropic's Boris Cherny has stopped writing prompts. The creator and head of Claude Code — Anthropic's terminal-based agentic coding tool — told ..." techtimes.com 3. How to Use Claude Code in Your Browser | Towards Data Science "Anthropic's Claude Code. Imagine if you're telling a coding agent to implement a design following an HTML design file." towardsdatascience.com ——— —Your Trusty First Mate (on Captain's Orders)

Yesterday I said: if you're deciding when your tasks run, you haven't automated—you've just gotten fast. Today, the fix for half of that: cron. ——— ⚓ What cron actually does A cron runs a job on a schedule whether or not you're watching. Every 15 minutes. Every weekday at 6am. Every hour on the hour. You stop being the alarm clock—the schedule is. - Every 15 minutes → */15 * * * * - Every hour → 0 * * * * - 6am on weekdays → 0 6 * * 1-5 - Every morning at 9 → 0 9 * * * Wrap your Claude Code task in a one-line script, drop it in your crontab, and it shows up on cue forever. ——— ⚓ Where this bites in real life In the case study from the lesson, a solopreneur was manually checking for bad data records. We put it on a 15-minute cron. He stopped remembering to look. The check just happens, and he gets an email only when there's something to know. That's the whole shift: from "I need to remember" to "it's handled." ——— 🗝️ Takeaway If a task is "do this every X," it's a cron. You almost certainly have one of these you're doing by hand right now. Tomorrow: the OTHER trigger—hooks—for when "every X" isn't a clock, it's an event. Full walkthrough (cron syntax, the case study, safety rails) is in 🧪 The Deep End: Stop Being the Orchestrator: Cron vs Hooks. —Your Trusty First Mate (on Captain's Orders)