<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vlad&apos;s Playbook — Chapters</title>
    <link>https://dive.vladyslavpodoliako.com/</link>
    <atom:link href="https://dive.vladyslavpodoliako.com/rss/chapters.xml" rel="self" type="application/rss+xml" />
    <description>A 58-chapter operator field manual for using AI tools in production.</description>
    <language>en</language>
    <lastBuildDate>Mon, 12 Oct 2026 00:00:00 +0000</lastBuildDate>
    <item>
      <title>The Conductor Never Codes</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/58-conductor-never-codes/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/58-conductor-never-codes/</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
      <description>In October 2026 I ran two product builds at once with agent swarms. Rightmark is a standalone data licensing product. Dylan is an AI SDR. Across 18 days I typed 223 prompts, the median one 52 characters. Each build&apos;s lead session was barred from writing product code: it planned, delegated and decided. Fresh verifiers reran every unit, refuters attacked every finding, and checkers outnumbered builders four to one. Rightmark merged through one lock and shipped 201 smoke-tested production deploys, and a watcher rolled back the attempt that broke sign-in. Make the session in charge a conductor, and turn every break into a gate before the next unit.</description>
    </item>
    <item>
      <title>Claude Code Mods</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/57-claude-code-mods/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/57-claude-code-mods/</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
      <description>A Claude Code mod is a plugin of function hooks that changes how Claude Code behaves or what it draws: a line above the prompt, a status line, a docked pane, a toast. Mods shipped on 1 October 2026. On 3 October I built six in 32 minutes, three rebuilt from the launch thread and three only my setup needed, each checked by the engine&apos;s own test runner before it touched a session. The tests caught four bugs. Then the guard I had just written blocked one of my own commands. Read your own setup before you copy a demo, and test the mod before you trust it.</description>
    </item>
    <item>
      <title>Read Before You Install</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/56-skill-leaderboard/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/56-skill-leaderboard/</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <description>A skill leaderboard ranks attention; what a skill costs sits where the board does not look. On 1 October I pointed a 23-agent swarm at one with 700 ranked repos. It read 118 repos from source, and I installed nine things: seven skills copied at the commit a vetter read and two pinned plugins. The seven add about 2,100 characters of description to every session&apos;s skill list; the 40 repos the lanes picked, installed whole, would have added 675,367. A review the next morning found gaps in my own plan, and nothing here measures a gain yet. Read the install, not the board.</description>
    </item>
    <item>
      <title>Claude Sonnet 5.5</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/55-claude-sonnet-5-5/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/55-claude-sonnet-5-5/</guid>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <description>Sonnet 5.5 shipped on 28 September at Sonnet 5&apos;s price, $2/$10 per million tokens, half of Opus 5.5 per token. On my planted-bug review it found all six bugs at high effort in both runs, with about half of Opus 5.5&apos;s output tokens at the same effort and 41% of its time. At low and medium it missed the same subtle bug four times out of four, and it never reported the real bugs nobody planted, which every Opus 5.5 run did. Run it at high for well-scoped work with a checkable finish, and keep Opus 5.5 for open-ended judgment.</description>
    </item>
    <item>
      <title>Claude Opus 5.5</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/54-claude-opus-5-5/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/54-claude-opus-5-5/</guid>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <description>Opus 5.5 is the model Anthropic now says to start with, and the one my Claude Code sessions have run since 22 September: $4/$20 per million tokens, 1M context, thinking always on, and effort as the only dial, defaulting to medium. On my planted-bug review, medium found all six bugs with less than half the output tokens of high, and xhigh spent more than twice the tokens and time of high for nothing more. Set effort on purpose, treat a text-only end of turn as a report rather than a finish, watch for refusals that arrive as HTTP 200, and migrate the API contract, not just the model string.</description>
    </item>
    <item>
      <title>The First Real Caller</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/53-first-real-caller/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/53-first-real-caller/</guid>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <description>I run an AI phone roleplay that assesses cold callers. On 29 September the first SDR from my own team called it, and in one morning production found three things 601 passing tests had not: a spelled surname that broke intake, callbacks that failed with no recorded reason, and a phone-line grader that scored him 14 to 30 points above a second review of the same calls. The first two fixes took minutes; the grader&apos;s is written and waits to be published on the phone line. Each find needed a real caller. Test with real speech, log the reason before you retry, and never let one model grade alone.</description>
    </item>
    <item>
      <title>What Agents Can&apos;t See</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/52-what-agents-cant-see/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/52-what-agents-cant-see/</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <description>Agents judge what they can read; users judge what they can see. I spent one working day on my menu-bar usage app with Claude Code and about 85 workflow agents. The first two review rounds read the code and caught two major bugs before either shipped, and the suite ended at 768 passing tests. The same process designed, built and reviewed a new menu from text descriptions, and nobody rendered a pixel until I sent a screenshot back. On my real wallpaper, an account at 0% then drew as full. Give every design stage rendered images, or it is reviewing a description.</description>
    </item>
    <item>
      <title>Jev and the System One Layer</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/51-jev-system-one/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/51-jev-system-one/</guid>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <description>Jev is a model that never writes text: you send it state and typed questions, it returns probabilities, and your code decides. I wired it into the Radar page&apos;s pipeline and measured it against a labelled set and a logistic regression trained on the same labels. It won the yes/no question by sixteen points and lost the eight-way one by eleven. Install it in five minutes, but ship nothing without a receipt.</description>
    </item>
    <item>
      <title>Claude Fable 5.1</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/50-claude-fable-5-1/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/50-claude-fable-5-1/</guid>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate>
      <description>Consider Fable 5.1 for difficult debugging and research-to-document work when a cheaper baseline misses a defined acceptance test. This is a source-backed guide, not a hands-on verdict. Pin the model ID, record the model that actually serves each step, approve enterprise data handling, and count cache writes, partial attempts, fallbacks, and review before deciding whether to switch.</description>
    </item>
    <item>
      <title>GPT-6 Astra: The Cost of a Finished Job</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/49-gpt-6-astra/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/49-gpt-6-astra/</guid>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate>
      <description>Trial Astra on difficult work with an inspectable finish line: a scoped patch, a cited decision brief, or a reconciled deliverable. Published benchmarks justify investigation, not a personal recommendation. These synthetic protocols are unrun; compare accepted outputs, total spend, and review time before changing your default model.</description>
    </item>
    <item>
      <title>The Traffic Graph That Lies</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/48-traffic-graph-that-lies/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/48-traffic-graph-that-lies/</guid>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate>
      <description>Most &apos;agentic SEO&apos; is a self-reported traffic graph that craters in six months — the operator who claimed 24k clicks in three months on a zero-backlink site, and the SEO veterans who called it vanity, were mostly right. So I pointed the swarm at Google across two AI-built products and pulled the real numbers. Folderly EmailGen is a genuine win: a brand-new subdomain hit #1 for &apos;business email generator,&apos; 467K impressions over the year, third-party traffic value climbing from ~$0 to ~$320/mo. LinguaLive is the cautionary tale: a 153K-impression graph that looks like a win until you see roughly nineteen of every twenty clicks are people already typing the brand name. The honest part is the divergence — Google&apos;s own console shows EmailGen 3.3K clicks across ~1,000 queries while Ahrefs sees 21 keywords; so you triangulate, and you don&apos;t trust a graph you can&apos;t independently check.</description>
    </item>
    <item>
      <title>The Measurement Layer</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/47-measurement-layer/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/47-measurement-layer/</guid>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <description>Chapter 25&apos;s three-line eval is a smoke detector for an internal skill&apos;s artifact. But when the model&apos;s output IS the product — a tutor&apos;s reply, a generated cold email — a boolean can&apos;t tell you if it&apos;s any good; you need a graded test set, and most builders skip it because it feels like research-team work. It isn&apos;t. Anthropic&apos;s own developer course ships the exact code: a way to SCORE output and a way to RETRIEVE the right context. I ported both to TypeScript in a weekend — a scorer that shows its failures and a hybrid retriever, 29 tests green. Pick measurement, or pick hope.</description>
    </item>
    <item>
      <title>Designing with AI</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/46-designing-with-ai/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/46-designing-with-ai/</guid>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <description>Generation went to zero — anyone can prompt a polished-looking page in seconds, which is exactly why every AI page looks the same. The scarce skill flipped from making an interface to choosing which one is right, and choosing is a judgment a generator can&apos;t make for you. This chapter proves it with this book&apos;s own receipts: a contrast failure that sat in our own light-theme tokens for weeks until the arithmetic caught what every eye had passed; the swarm-before-v1 discipline; a design system as the ruler that tames model drift; and flicked.email — one product with three live landing pages (chaos, hype, calm) in three different heading typefaces, all AI-built, where only a human can say which intent is true. First-person here is Claude and Claude Code; every other tool is labeled researched. The final section turns the same discipline on AI image generation — art direction as intent for pixels, encoded as a public taste skill, with a moon-base concept set for Reach as the worked example. Taste is the last mile, the system is taste externalized, and the last mile is the whole job now.</description>
    </item>
    <item>
      <title>The App Store Without Swift</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/45-app-store-no-swift/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/45-app-store-no-swift/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <description>Claude Code one-shot every line of native SwiftUI for LinguaLive — and still could not ship it. The App Store is just another deploy target, but with the strictest gates in the book, and the operator, not the agent, walks through every one: a Mac with Xcode, the $99/yr membership, the signing maze, the account-deletion rule, the App Privacy label, a working demo login for the reviewer. The lesson is not &apos;you can build iOS with no Swift&apos; — the code is the easy part now. It&apos;s that shipping native means owning the platform-and-policy surface the agent is structurally locked out of. The proof isn&apos;t a download count — it&apos;s one RevenueCat row where an INITIAL_PURCHASE became a RENEWAL: $7.99 that recurred on its own, because a real StoreKit purchase ran on a real phone. Read honestly, that row proves recurring revenue and a stacking renewal — not total scale.</description>
    </item>
    <item>
      <title>Dreaming — Memory That Curates Itself</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/44-dreaming/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/44-dreaming/</guid>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <description>Dynamic workflows impressed me by holding a whole task&apos;s memory in a two-hundred-line script. That made me ask the harder question: what holds MY memory across hundreds of sessions? Rick&apos;s been dreaming on a Mac mini for months — OpenClaw logic, multiple models, dated files. Anthropic shipped Dreaming as an agent that writes its own memory. I built the Claude Code version deliberately weaker: propose-only. It digests sessions outside the model, fans out read-only agents that each cite a verbatim quote, re-verifies every quote against the raw transcript, and writes a review file I skim — it never writes to memory itself. Memory is the moat, and the moat is a lot of work.</description>
    </item>
    <item>
      <title>Codex as Saviour</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/43-codex-saviour/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/43-codex-saviour/</guid>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <description>Codex pointed at a real product with one constraint — simplify, follow the design system — deleted a net 91,874 lines across 718 files, repositioned the product to one promise, and hardened the risky paths it exposed, all behind real build, CI, browser, and API checks. Simplification and security turn out to be the same phase.</description>
    </item>
    <item>
      <title>Codex on a Loop</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/42-codex-on-a-loop/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/42-codex-on-a-loop/</guid>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <description>Codex isn&apos;t a better Claude Code — it&apos;s a second prior I run on a loop. Pointed at Sentry + PostHog + BetterStack via MCP and crons, it fixes fresh signals in worktree-isolated PRs, proof-checks the day driver&apos;s diffs by running the tests CC didn&apos;t think to run, and — one afternoon, in about ten minutes — hatched a desktop pet from a cross-vendor skill. Best execution is always a second opinion plus a proof check, never one agent trusted blind.</description>
    </item>
    <item>
      <title>Send the Link, Not the File</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/41-send-the-link/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/41-send-the-link/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <description>Every report, pitch, audit, deck, and model in my portfolio ships as a live interactive HTML link in a private repo, not as a PDF or slide attachment. The cheaper, better, more current artifact also happens to be the one that takes less of your night. This chapter is the thesis; /html-first is the deep reference with the embedded case studies, the recipe, the applications gallery, and the twelve public examples in the wild.</description>
    </item>
    <item>
      <title>Prompting, or the Knob You Probably Shouldn&apos;t Tune</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/40-prompting-knob/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/40-prompting-knob/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <description>Prompting is a basic skill now — necessary, table stakes, not the lever. The leverage moved up the ladder: skills, swarms, memory, and the data layer underneath. Most prompt-engineering content is written for benchmark scores, not for whether the workflow still runs on Tuesday morning. This chapter is what to keep, what to drop, and where the real leverage actually lives — with one of my own published prompts as the worked example of both.</description>
    </item>
    <item>
      <title>Skills You Should Steal (and the Three You Should Write Yourself)</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/39-skills-you-should-steal/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/39-skills-you-should-steal/</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <description>By May 2026 the public skills ecosystem crossed a million entries — and a dev.to audit found 73% of them silently broken. The fix isn&apos;t installing more, it&apos;s knowing which nine libraries to steal from and which three gap-filling skills no one&apos;s written yet. Star count is not a security signal.</description>
    </item>
    <item>
      <title>Run Until Done</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/38-run-until-done/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/38-run-until-done/</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <description>/goal landed in Claude Code v2.1.139 on May 11, 2026, and it changes the unit of human approval from per-step to per-outcome. With /loop and Stop hooks alongside it, the autonomous-loop surface is finally a clean three-way — evaluator-driven, interval-driven, custom-logic-driven. Pick the wrong one and the agent loops forever; pick the right one and your Saturday gets shorter.</description>
    </item>
    <item>
      <title>Context Files — CLAUDE.md, memory, skills</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/37-context-files/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/37-context-files/</guid>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <description>Prompt engineering is the visible part. Context-file architecture is the load-bearing part nobody writes about. CLAUDE.md is the kitchen rules taped to the wall. memory/ is the notebook the agent writes to. Skills are the recipes pulled on demand. Get the layers wrong and the model ignores all of them.</description>
    </item>
    <item>
      <title>When Do I Outgrow Claude Code?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/36-frameworks-beyond/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/36-frameworks-beyond/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>Five Claude Code subagents kept stepping on each other in a deal-research workflow because they all wrote to the same scratchpad. CrewAI cracked it with explicit handoff contracts. LangGraph cracked the next one with explicit state. The graduation from CC to a framework isn&apos;t about power — it&apos;s about contracts the orchestrator enforces instead of you.</description>
    </item>
    <item>
      <title>Codex or Claude Code — or Both?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/35-codex-and-cc/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/35-codex-and-cc/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>Codex opens a PR at 3 AM against the Belkins Sentry stream. I review and merge it in Claude Code at 9. Same repo, same .mcp.json, same CLAUDE.md — two agents, two contracts, one shift hand-off. The hard part isn&apos;t picking a model; it&apos;s keeping the night shift and the day shift from stepping on each other.</description>
    </item>
    <item>
      <title>Persona Agents and the Four NEVERs</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/34-write-on-behalf/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/34-write-on-behalf/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>At 9:14 AM Tuesday a Slack message went out under my name in my voice — drafted by an agent that read the thread, waited 6 minutes for me to type &apos;yes,&apos; and posted. Two weeks earlier the same agent didn&apos;t wait, posted to a co-founder a quarter answer to a half question, and he called me about it within four minutes. The unlock is voice fidelity. The non-negotiable is the approval gate.</description>
    </item>
    <item>
      <title>Browser Agents with Playwright</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/33-browser-agents/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/33-browser-agents/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>At 4:11 AM a Playwright script logged into a competitor&apos;s pricing page, diffed it against yesterday, and posted to Slack while I slept. Two days later the same agent posted into the wrong channel and a customer saw a screenshot of someone else&apos;s pricing. Both halves of that week are the chapter — what browser agents unlock, and the rails you bolt on so they don&apos;t bite the company that built them.</description>
    </item>
    <item>
      <title>Agent Archetypes (Rick Platform)</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/32-archetypes-rick/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/32-archetypes-rick/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>I onboarded a Belkins SDR onto a NemoClaw in three days — prior baseline was eleven. Rick is the archetype layer: pre-shaped agents that show up knowing what kind of job they&apos;re for. Pick the preset, plug in your accounts, ship. Graduate to a custom subagent later, when the preset starts costing you more than it saves.</description>
    </item>
    <item>
      <title>Six Stages from Idea to Deploy</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/31-stages/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/31-stages/</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <description>I caught myself painting trim before the foundation was poured, on a Saturday, on my own time, on a project I cared about. Six stages — Ideation, Foundation, Creation, Polishing, Security, Deploy — and the order is the whole game. Skip one and the Saturday dies.</description>
    </item>
    <item>
      <title>When to Drop CC for the SDK</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/30-sdk-direct/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/30-sdk-direct/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>A customer asked if the AI feature in their dashboard could run without me opening Claude Code. The honest answer was no — what they saw was a skill in my session, not a feature in their product. I wrote 34 lines of Python against the Anthropic SDK and shipped that afternoon. It&apos;s been serving customers for nine months. This chapter is what&apos;s inside those 34 lines.</description>
    </item>
    <item>
      <title>Why Is My Bill So High?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/29-cost-economics/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/29-cost-economics/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>My Anthropic bill went from $1,108 a week to $4,312 a week with zero workload change. The culprit was a 38-line CLAUDE.md edit that voided prompt caching on 60% of my morning briefings. The fix took 12 minutes. Knowing the fix existed took six months. This chapter is so you don&apos;t have to wait six months.</description>
    </item>
    <item>
      <title>Six Failures, Six Bills</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/28-failure-receipts/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/28-failure-receipts/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>$1,847 in eleven hours from a recursion I didn&apos;t catch. A skill that wrote to the wrong vault for nine days. A connector that exfiltrated a customer email. None of these showed up on a tier list. All of them changed how I run things.</description>
    </item>
    <item>
      <title>Voice Agents — STT, LLM, TTS</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/27-voice-agents/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/27-voice-agents/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>A LinguaLive prototype answered an investor call on the third ring and went silent for 1.4 seconds before it spoke. The model wasn&apos;t slow — the stack was. Voice agents fail politely, and polite failure is what costs you the deal.</description>
    </item>
    <item>
      <title>How Do I Get My Team to Adopt?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/26-team-adoption/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/26-team-adoption/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>I shipped a Cowork briefing skill to twelve sales reps and by 9:47 AM the rollout had already split into a 4-3-2-2-1 distribution that nobody warns you about. Tools don&apos;t adopt themselves and the early adopter is your worst onboarding partner. The team CLAUDE.md, skills as policy, and a 30-day metric that isn&apos;t usage.</description>
    </item>
    <item>
      <title>Evals — Smoke, Regression, Golden</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/25-evals-or-hope/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/25-evals-or-hope/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>A skill shipped a $0-pipeline canvas to my COO and stayed broken for nine days because no eval was watching. Start with a small artifact check, then gate every delivery on validated inputs and output. An earlier dry run is useful warning, not permission to publish a later unchecked result.</description>
    </item>
    <item>
      <title>The Tier List</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/24-tier-list/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/24-tier-list/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Three tier lists — AI tools, connectors, and infra — ranked without diplomatic phrasing. The stack changes every six months. The thing that&apos;s actually S-tier is the discipline. The tools are leverage. The discipline is the lever.</description>
    </item>
    <item>
      <title>A Saturday Build, Hour by Hour</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/23-vibe-coding/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/23-vibe-coding/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Eight hours, $72 in tokens, six bugs hit and fixed, one shipped pipeline. Hour-by-hour log of a real Saturday build with the misfires kept in — including the rabbit holes the Don&apos;ts list killed before they started.</description>
    </item>
    <item>
      <title>Resume, Replay, Fork</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/22-sessions/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/22-sessions/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Sessions in Claude Code are a filesystem, not a memory. Resume picks up where you left off. Fork preserves the original timeline and grows a new branch. The session remembers this morning. The vault remembers your career.</description>
    </item>
    <item>
      <title>Which Mode Right Now?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/21-three-modes/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/21-three-modes/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Four modes now, one tool, four completely different relationships with the agent. Plan → Interactive → Auto was the stack; /goal added a fourth in May 2026 that removes per-turn approval the way Auto removed per-tool approval. Most operators run Claude Code in the wrong mode for the job and lose either time or money. Pick the mode that matches the cost of a wrong action — not the urgency.</description>
    </item>
    <item>
      <title>tmux, Worktrees, Named Sessions</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/20-terminal-windows/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/20-terminal-windows/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Four panes, four agents, one human conducting. The terminal becomes an org chart and you become the CEO. tmux + named sessions + git worktrees is the trick that turns a single laptop into a small team.</description>
    </item>
    <item>
      <title>Shipping a Product in a Saturday</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/19-build-products/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/19-build-products/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>One operator ships a real, deployed voice-brief product in a single Saturday — four hours of hands-on work, $80 in tokens, zero salary. The compounding doesn&apos;t show up in the spend column. It shows up in the calendar.</description>
    </item>
    <item>
      <title>Headless Claude and CI</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/18-headless-ci/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/18-headless-ci/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>The real unlock is claude --print. Same binary as the IDE chat, runs as a deploy step, a GitHub Action, a 3 AM cron job. Going from &apos;I run claude in my terminal&apos; to &apos;Claude is part of my infrastructure&apos; is one flag — and one mental shift from driving to scheduling.</description>
    </item>
    <item>
      <title>25 Operator Tips</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/17-tips-tricks/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/17-tips-tricks/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>None of this is in the docs because none of it is teachable until you&apos;ve shipped a few hundred hours through the agent. Twenty-five tips in five buckets — context, cost, permissions, tooling, habits. I learned each the dumb way. You don&apos;t have to.</description>
    </item>
    <item>
      <title>Hooks and Custom Subagents</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/16-hooks-subagents/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/16-hooks-subagents/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Hooks turn ad-hoc prompting into policy. Subagents turn one model into a team. Together, they&apos;re how you stop talking to Claude and start operating it.</description>
    </item>
    <item>
      <title>When to Skip Permissions</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/15-permissions/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/15-permissions/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>There&apos;s a flag called --dangerously-skip-permissions. The name is the warning label. People still type it on their main machine, watch their .env get rewritten, and learn the hard way. This chapter is so you don&apos;t — and so you know what to do when you do.</description>
    </item>
    <item>
      <title>Slash Commands and Settings</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/14-cheat-sheet/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/14-cheat-sheet/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>The ten-minute version of every Claude Code search history — flags, slash commands, settings keys, env vars, file paths. Bookmark it. You&apos;ll come back.</description>
    </item>
    <item>
      <title>Claude Code in 10 Minutes</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/13-quickstart/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/13-quickstart/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Install Claude Code, verify the installation, and run one read-only task in a test repo. Allow about ten minutes with an account and terminal ready; authentication or troubleshooting can take longer. Connectors are an optional next step.</description>
    </item>
    <item>
      <title>Connectors and MCP</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/12-connectors-mcp/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/12-connectors-mcp/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>An AI agent without connectors is a chef with no kitchen — it can describe a meal but can&apos;t cook. MCP is the USB-C of AI tools: one port, every device. Here&apos;s the full taxonomy, the install path for Cowork and Claude Code, and the 50-line custom server you can write in an evening.</description>
    </item>
    <item>
      <title>Build a Skill in 30 Minutes</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/11-build-a-skill/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/11-build-a-skill/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>A skill is a folder. SKILL.md is the only required file. After 20 of them, you stop prompting and start calling functions. Here&apos;s the morning-briefing skill, written end to end — description, body, scripts, anti-patterns, the test loop, and the five ways skills fail.</description>
    </item>
    <item>
      <title>Hosted Agents, Local Models, Frontier</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/10-wild-stuff/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/10-wild-stuff/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>It&apos;s 2:14 AM in London and one operator is directing a generative video pipeline that would have required a studio a year ago. The leverage isn&apos;t in any single tool — it lives in the seams. Here&apos;s the menu, the hardware reality, and the seven-step shape of the day you stop reading about this and start operating in it.</description>
    </item>
    <item>
      <title>Blast Radius and Key Hygiene</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/09-dont-get-owned/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/09-dont-get-owned/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Eleven minutes — that&apos;s how long it took for a leaked Stripe key to drain $4,200 from a friend&apos;s startup. Agents are 10x contractors and 10x attack surfaces; the part that doesn&apos;t get airtime in keynotes is what&apos;ll wake you up at 3 AM. Skim this chapter least; read it most.</description>
    </item>
    <item>
      <title>Chat, Cowork, or Claude Code?</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/08-three-doors/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/08-three-doors/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Same model, three surfaces. Most operators have one Claude tab open and think Claude is one thing. Sedan, SUV, pickup — knowing which one to drive when is half the unlock. Get the choice wrong and you spend an hour on what should take ten minutes.</description>
    </item>
    <item>
      <title>Scheduled Tasks</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/07-cron/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/07-cron/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Synchronous AI is a vending machine — useful only when you walk up to it. Scheduled tasks turn AI into a chef who preps meals before you sit down. The Saturday canvas that closes your week, the morning brief that lands before your coffee — they&apos;re not bigger models. They&apos;re scheduling decisions.</description>
    </item>
    <item>
      <title>Parallel Subagents and Fan-Out</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/06-the-swarm/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/06-the-swarm/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>This 25,000-word book was written by 15 AI agents in parallel in six minutes wall-clock for under $40. Once you&apos;ve used a swarm, sequential work feels like writing email by candlelight. The model didn&apos;t get smarter that morning — the architecture got smarter. You don&apos;t need a bigger model. You need a conductor&apos;s mindset.</description>
    </item>
    <item>
      <title>What a Skill Is</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/05-skills/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/05-skills/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>If you&apos;re re-explaining the same workflow to Claude every time, you&apos;re paying full cognitive cost on every order. Skills are the recipe card pinned above the burner — a folder, a SKILL.md, a description that fires when you need it. Skills are the difference between using AI and operating AI.</description>
    </item>
    <item>
      <title>Obsidian as Working Memory</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/04-the-vault/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/04-the-vault/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>My paid mentee has been feeling my AI&apos;s work for over a year and has never met it. The trick is a vault — folder of markdown files I hand every fresh instance on wake-up. Without it, the model is a genius with amnesia. With it, you have an OS that compounds for years.</description>
    </item>
    <item>
      <title>Why Claude Forgets You</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/03-temp-agency/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/03-temp-agency/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>The single most expensive cognitive error in modern business is treating AI like a coworker you&apos;re slowly training. It isn&apos;t. Every session is a fresh temp on day one — sharp, capable, amnesiac. Once that lands, you stop hoarding chat history and start running a workforce.</description>
    </item>
    <item>
      <title>The Five-Tool Stack</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/02-five-tools/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/02-five-tools/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>I get asked once a week what&apos;s in my stack. People want a list of thirty. The honest answer is five. Each tool plays one role — head chef, sous chef, walk-in fridge, mobile cook, voice — and the discipline is refusing to blur them. Surface area is the enemy.</description>
    </item>
    <item>
      <title>AI as an Operating System</title>
      <link>https://dive.vladyslavpodoliako.com/chapters/01-killed-my-tabs/</link>
      <guid isPermaLink="true">https://dive.vladyslavpodoliako.com/chapters/01-killed-my-tabs/</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <description>Three instances ran while I slept and dropped a finished morning brief in one Slack channel. The unlock isn&apos;t AI doing my work faster — it&apos;s AI deleting my context-switching across forty open tabs. Stop visiting a chatbot. Start living inside an OS.</description>
    </item>
  </channel>
</rss>
