Gnothi Claude Code
by OCDevel
10. Work That Keeps Running After You Close the Laptop
About this podcast
Take Claude Code from its first useful change in your terminal to a repeatable software delivery workflow. For working developers who already ship applications and use Git, this course starts with setup, giving Claude a task, inspecting the diff and checking the result. Build on that session with project instructions, skills, hooks, MCP connections and context management. Later lessons connect parallel agents and Git worktrees to GitHub issues, pull requests and review-and-fix loops, then develop testing and deployment workflows with GitHub Actions and AWS. Permissions, sandboxing, cost controls and observability are taught alongside the automation they support, so you can judge what a run changed and investigate a failure. Concrete examples explain the commands, settings and checks behind each workflow; earlier techniques return as parts of larger systems. Claude Code news and practical shortcuts cover changes that affect coding work, setup or cost. The curriculum builds toward an issue-to-deployment pipeline, including rollout decisions and incident response. This show's audio is narrated by AI-generated synthetic voices.
Episodes
- 10. Work That Keeps Running After You Close the LaptopCompares remote control, hosted cloud sessions and headless runs for what happens when the laptop closes, then walks through finishing the shared-list app's issue thirteen as a…
- 9. A Second Pair of Eyes That Cannot EditBuilds a read-only Claude Code subagent that checks a diff against a GitHub issue's acceptance criteria, tests it on a good and a deliberately broken change, and weighs it…
- 8. A Baseline for Judging the Agent's SetupHow to build a small baseline of real tasks with known answers, and use it to choose a Claude model and effort level by the total cost of finished work, including your review and…
- 7. Letting the Agent Read the Issue ItselfA fast-add bug becomes a GitHub issue that Claude Code reads through GitHub's MCP server, with read, comment and delete tools each given their own permission. The bug is then…
- 6. Writing a Method Down Once as a SkillBuilding a Claude Code skill that turns bug reports into a four-part reproduction note before any code changes, including how skills differ from CLAUDE.md and hooks and how to…
- 5. A Check That Runs Without Being AskedMoving the type check from something you remember to run into a PostToolUse hook that Claude Code runs after every edit, feeding errors back so the agent fixes them before…
- 4. A Change Too Big for One SessionHow to carry a multi-step change across several Claude Code sessions by keeping its plan, decisions and progress in committed files. It covers continue and resume, reading…
- 3. Fixing a Bug in Code You Have Never ReadA vague pasted-text bug report gets turned into a reproduction, then traced with an agent that is blocked from editing anything, then fixed one narrow diff at a time. Includes…
- 2. Writing the Instructions Your Next Session Will Actually ReadThis chapter explains how to write and test a CLAUDE.md file so a fresh Claude Code session knows a project's commands, layout, and definition of done without being told each…
- 1. Your First Real Change, Made by an Agent and Checked by YouThis chapter installs Claude Code, opens it inside a small shared-list web app, and walks through fixing one real bug — blank items being addable — end to end: describing the…







