Guide Patriolas (96 results)

Paperback. Condition: new. Paperback. You already run Claude every day, and you've hit the ceiling: Every session opens blind. It wakes up knowing nothing about your projects, your machines, or what you settled yesterday, so you burn the first ten minutes re-explaining yourself before any real work starts. Run one project and that's a mild tax. Twenty, and it's a part-time job. This book is the operating system the author runs to kill that tax - the plumbing a session uses to load its own context and hand off cleanly to the next one, across every project on the drive. You wire it once and stop thinking about it. This is for advanced users who are comfortable in the Claude Code CLI. Nine chapters, each a working part of one system: a launcher that opens Claude already scoped to the right projectaSESSION_LOADER that tells the model where everything lives and what it must never reada SessionStart hooks that inject the right context for each kind of session, before your first messagea /start routine that reports the three facts that matter and skips the restcapturing ideas and tasks mid-session without switching appsbending the whole system to fit your real inputs, whether that's a task queue, an inbox, or a ticket toolsurviving compaction with a baton that carries state across the context cutstanding rules that end the re-explaining for good, plus how to prune the ones that go stalerunning Claude across a laptop, a GPU box, and anything else you can SSH intoEvery example is a real working piece of the author's daily practice, with the private paths swapped for generic ones. Nothing is invented to illustrate a point. If it's in the book, it runs. This is the advanced shelf. You live in the Claude Code CLI, you read a script without flinching, and you're done being a tourist in your own tools. By the end, your sessions carry their own context, and you start where you left off instead of starting over. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condition: new. Paperback. Two paths to a voice that sounds like you. This book teaches both and is honest about what each one costs. The fast path is free. Upload thirty seconds of clean audio to a HuggingFace Space and a clone comes back - without a GPU, a training run, or any setup. A recognizable voice arrives in an afternoon. Delivery is flat, emotion absent, and you own nothing - for a demo or a quick test, that is often enough, and the book says so plainly. The thorough path takes hours of recordings, a rented GPU, and real money. What comes out is a model you own and serve yourself, with emotional range built from a labeled dataset you designed. It can sound tired or sharp or dry. Flat neutral is the floor and the model has headroom above it. Getting there requires a dataset prep pipeline, a training run on rented hardware with billing guards so a failed job does not keep charging, a checkpoint retrieval, and a serving wrapper running on a machine you control. This book covers both paths in full. The fast path is chapter one. Everything after is the thorough path. Claude runs the pipeline for the thorough path: dataset prep automation (silence trim, normalization, format conversion, metadata write), training config generation, run monitoring, checkpoint evaluation, server startup, and the verification pass that signs off before a checkpoint goes to production. The model trainer does the learning. Claude handles everything around it. Chapter coverage: the fast clone first - what zero-shot cloning is, what the reference recording must clear, and where this path ends. Dataset architecture next - the real recording numbers, the folder structure and metadata format XTTS expects, and the prep pipeline including the 44.1 kHz record / 22.05 kHz train split. Training on rented hardware: the EC2 bootstrap, the 8-fix hardening pass drawn from real failed runs, the shutdown-on-exit billing guard, and the S3 checkpoint storage pattern. Reading the run: loss curves, checkpoint selection, retrieving results after the instance terminates. Serving: pulling the checkpoint to a local GPU machine, the Flask endpoint, inference calls from other pipelines. Verification: acoustic checks, the listen test, the sign-off gate. Raw to served in the final chapter - one complete session transcript showing every seam. Written for operators who already run Claude Code across real projects and want a voice in their pipeline they actually own - and want to know exactly what that costs before committing to it. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condition: new. Paperback. "Claude finished" and "it's right" are two different sentences. Most pipelines treat them as the same one. Work exits clean, a mistake ships with it, and you find out later. This book installs the system that closes that gap: quality gates that take a concrete measurement and stop the pipeline when it fails. These gates come from a production stack used to ship every book in this series, a live website, and a multi-agent system. The LIKE Engine catches rhetorical device tells before a chapter advances. Running in parallel, the ARC Engine catches statistical and grammatical tells. A deploy script verifies the live URL returns 200 and the md5 matches before any book gets marked done. Sign-off requires actual gate results - not a gut feeling. None of these are prompts. They are code with exit codes, and the pipeline stops at the first nonzero one. The book gives you a precise vocabulary for talking about gates and a pattern for installing them at the right layer of anypipeline, whether the output being gated is prose, deployed files, generated code, or structured data. One complete worked example - the book production stack - shows every layer wired in and explained. The gates are specific; the pattern generalizes. This book is a specimen of what it teaches. Every chapter passed the LIKE + ARC gate pair before it was committed. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condition: new. Paperback. Your laptop isn't the limit - it's just where you start. This book shows how to extend your Claude workflow to a second machine: run sessions remotely so your laptop stays cool, hand GPU-intensive jobs to hardware that can handle them, and use SSH + Claude to build things for other people on their own machines. Every pattern is drawn from a production setup that runs voice training, overnight batch jobs, and remote builds on demand. The setup is practical and unglamorous: key-based SSH auth, Claude CLI installed on the remote, rsync to move files, tmux to keep sessions alive after you disconnect. The architecture is simple - laptop describes the work, remote executes it, results come back - and once it's running you rarely think about it. You give the heavy job to the machine that can handle it and come back when it's done. Chapter by chapter: set up the SSH connection and verify it holds; install and authenticate Claude on the remote; move files reliably and keep sessions alive overnight; hand GPU workloads to the hardware that was built for them; use the same pattern to build things for someone else on their own machine; then run the whole system in one complete session from start to finish. Every chapter adds one layer. The reader can stop after any of them and have something working. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Condition: New. Print on Demand.

Condition: New. Print on Demand.

Condition: New. Print on Demand.

Condition: New. Print on Demand.

Paperback. Condition: new. Paperback. Your agents have inboxes. They still can't talk. Book 5 gave you the inbox pattern - agents write messages instead of calling each other directly. What it didn't give you is a messaging layer: a schema those messages must follow, an archivist to route them to the right agent, a rule preventing one agent from writing directly into another's state files, and a dispatcher that works even when the target node has no active session. This book builds that layer. Seven chapters, one pattern each, one deployable artifact each. By the end you have schema-validated envelopes, a working archivist, a write-prohibition rule enforced structurally, versioned schemas that survive agent updates, a cross-node dispatcher that queues instead of failing, an append-only event log that reconstructs any failure, and a multi-agent deliberation protocol for decisions that need independent perspectives. Every pattern comes from real infrastructure. Every artifact runs the day you build it. Prerequisite: Books 5 (AI Teams) and 7 (Self-Verifying Pipelines), or equivalent experience building multi-agent Claude Code systems with role contracts, inboxes, and quality gates. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condition: new. Paperback. Every Claude Code session burns tokens. Most operators don't know how many until the quota runs out. This book builds the cost-control layer for CLI operators - the people running Claude Code directly, not the SDK. It is not about API-level prompt caching. Chapter 1 says so plainly, explains what prompt caching is and why it doesn't apply here, and moves on to what does: the three levers a CLI operator actually controls. From there, seven chapters each deliver one working piece of the cost-control stack. Chapter 2 shows how to read what sessions actually cost, building a session cost log that makes spend visible. Chapter 3 turns the PreCompact baton into a cost gate - the hook that fires when context approaches the window limit becomes the moment you decide whether to continue or stop. Chapter 4 builds a model router that sends work to the right tier: Haiku for lookups, Sonnet for standard tasks, Opus for work that earns the price. Chapter 5 installs budget gates that stop pipelines before they blow the cap - a hard stop, a soft warning, and a config file that sets the thresholds. Chapter 6 separates cost by project, so one runaway job can't drain the quota for everything else. Chapter 7 ties the pieces together into a cost-aware pipeline design - the habits and structural patterns that keep spend predictable across every session you run. By the last chapter you have a cost-control stack running beneath your workflows. Spend is visible, routed, and bounded. The quota surprise stops. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Taschenbuch. Condition: Neu. Neuware - Two paths to a voice that sounds like you. This book teaches both and is honest about what each one costs. The fast path is free. Upload thirty seconds of clean audio to a HuggingFace Space and a clone comes back - without a GPU, a training run, or any setup. A recognizable voice arrives in an afternoon. Delivery is flat, emotion absent, and you own nothing - for a demo or a quick test, that is often enough, and the book says so plainly. The thorough path takes hours of recordings, a rented GPU, and real money. What comes out is a model you own and serve yourself, with emotional range built from a labeled dataset you designed. It can sound tired or sharp or dry. Flat neutral is the floor and the model has headroom above it. Getting there requires a dataset prep pipeline, a training run on rented hardware with billing guards so a failed job does not keep charging, a checkpoint retrieval, and a serving wrapper running on a machine you control. This book covers both paths in full. The fast path is chapter one. Everything after is the thorough path. Claude runs the pipeline for the thorough path: dataset prep automation (silence trim, normalization, format conversion, metadata write), training config generation, run monitoring, checkpoint evaluation, server startup, and the verification pass that signs off before a checkpoint goes to production. The model trainer does the learning. Claude handles everything around it. Chapter coverage: the fast clone first - what zero-shot cloning is, what the reference recording must clear, and where this path ends. Dataset architecture next - the real recording numbers, the folder structure and metadata format XTTS expects, and the prep pipeline including the 44.1 kHz record / 22.05 kHz train split. Training on rented hardware: the EC2 bootstrap, the 8-fix hardening pass drawn from real failed runs, the shutdown-on-exit billing guard, and the S3 checkpoint storage pattern. Reading the run: loss curves, checkpoint selection, retrieving results after the instance terminates. Serving: pulling the checkpoint to a local GPU machine, the Flask endpoint, inference calls from other pipelines. Verification: acoustic checks, the listen test, the sign-off gate. Raw to served in the final chapter - one complete session transcript showing every seam. Written for operators who already run Claude Code across real projects and want a voice in their pipeline they actually own - and want to know exactly what that costs before committing to it.…

Taschenbuch. Condition: Neu. Neuware - Your laptop isn't the limit - it's just where you start. This book shows how to extend your Claude workflow to a second machine: run sessions remotely so your laptop stays cool, hand GPU-intensive jobs to hardware that can handle them, and use SSH + Claude to build things for other people on their own machines. Every pattern is drawn from a production setup that runs voice training, overnight batch jobs, and remote builds on demand. The setup is practical and unglamorous: key-based SSH auth, Claude CLI installed on the remote, rsync to move files, tmux to keep sessions alive after you disconnect. The architecture is simple - laptop describes the work, remote executes it, results come back - and once it's running you rarely think about it. You give the heavy job to the machine that can handle it and come back when it's done. Chapter by chapter: set up the SSH connection and verify it holds; install and authenticate Claude on the remote; move files reliably and keep sessions alive overnight; hand GPU workloads to the hardware that was built for them; use the same pattern to build things for someone else on their own machine; then run the whole system in one complete session from start to finish. Every chapter adds one layer. The reader can stop after any of them and have something working.…

Taschenbuch. Condition: Neu. Neuware - You already run Claude every day, and you've hit the ceiling: Every session opens blind. It wakes up knowing nothing about your projects, your machines, or what you settled yesterday, so you burn the first ten minutes re-explaining yourself before any real work starts. Run one project and that's a mild tax. Twenty, and it's a part-time job. This book is the operating system the author runs to kill that tax - the plumbing a session uses to load its own context and hand off cleanly to the next one, across every project on the drive. You wire it once and stop thinking about it. This is for advanced users who are comfortable in the Claude Code CLI. Nine chapters, each a working part of one system: - a launcher that opens Claude already scoped to the right project- aSESSION_LOADER that tells the model where everything lives and what it must never read- a SessionStart hooks that inject the right context for each kind of session, before your first message- a /start routine that reports the three facts that matter and skips the rest- capturing ideas and tasks mid-session without switching apps- bending the whole system to fit your real inputs, whether that's a task queue, an inbox, or a ticket tool- surviving compaction with a baton that carries state across the context cut- standing rules that end the re-explaining for good, plus how to prune the ones that go stale- running Claude across a laptop, a GPU box, and anything else you can SSH into>This is the advanced shelf. You live in the Claude Code CLI, you read a script without flinching, and you're done being a tourist in your own tools. By the end, your sessions carry their own context, and you start where you left off instead of starting over.…

Taschenbuch. Condition: Neu. Neuware - 'Claude finished' and 'it's right' are two different sentences. Most pipelines treat them as the same one. Work exits clean, a mistake ships with it, and you find out later. This book installs the system that closes that gap: quality gates that take a concrete measurement and stop the pipeline when it fails. These gates come from a production stack used to ship every book in this series, a live website, and a multi-agent system. The LIKE Engine catches rhetorical device tells before a chapter advances. Running in parallel, the ARC Engine catches statistical and grammatical tells. A deploy script verifies the live URL returns 200 and the md5 matches before any book gets marked done. Sign-off requires actual gate results - not a gut feeling. None of these are prompts. They are code with exit codes, and the pipeline stops at the first nonzero one. The book gives you a precise vocabulary for talking about gates and a pattern for installing them at the right layer of anypipeline, whether the output being gated is prose, deployed files, generated code, or structured data. One complete worked example - the book production stack - shows every layer wired in and explained. The gates are specific; the pattern generalizes. This book is a specimen of what it teaches. Every chapter passed the LIKE + ARC gate pair before it was committed.…

Condition: New. Print on Demand.

Condition: New. Print on Demand.

Taschenbuch. Condition: Neu. Neuware - Every Claude Code session burns tokens. Most operators don't know how many until the quota runs out. This book builds the cost-control layer for CLI operators - the people running Claude Code directly, not the SDK. It is not about API-level prompt caching. Chapter 1 says so plainly, explains what prompt caching is and why it doesn't apply here, and moves on to what does: the three levers a CLI operator actually controls. From there, seven chapters each deliver one working piece of the cost-control stack. Chapter 2 shows how to read what sessions actually cost, building a session cost log that makes spend visible. Chapter 3 turns the PreCompact baton into a cost gate - the hook that fires when context approaches the window limit becomes the moment you decide whether to continue or stop. Chapter 4 builds a model router that sends work to the right tier: Haiku for lookups, Sonnet for standard tasks, Opus for work that earns the price. Chapter 5 installs budget gates that stop pipelines before they blow the cap - a hard stop, a soft warning, and a config file that sets the thresholds. Chapter 6 separates cost by project, so one runaway job can't drain the quota for everything else. Chapter 7 ties the pieces together into a cost-aware pipeline design - the habits and structural patterns that keep spend predictable across every session you run. By the last chapter you have a cost-control stack running beneath your workflows. Spend is visible, routed, and bounded. The quota surprise stops. …

Taschenbuch. Condition: Neu. Neuware - Your agents have inboxes. They still can't talk. Book 5 gave you the inbox pattern - agents write messages instead of calling each other directly. What it didn't give you is a messaging layer: a schema those messages must follow, an archivist to route them to the right agent, a rule preventing one agent from writing directly into another's state files, and a dispatcher that works even when the target node has no active session. This book builds that layer. Seven chapters, one pattern each, one deployable artifact each. By the end you have schema-validated envelopes, a working archivist, a write-prohibition rule enforced structurally, versioned schemas that survive agent updates, a cross-node dispatcher that queues instead of failing, an append-only event log that reconstructs any failure, and a multi-agent deliberation protocol for decisions that need independent perspectives. Every pattern comes from real infrastructure. Every artifact runs the day you build it. Prerequisite: Books 5 (AI Teams) and 7 (Self-Verifying Pipelines), or equivalent experience building multi-agent Claude Code systems with role contracts, inboxes, and quality gates.…

Taschenbuch. Condition: Neu. Neuware - Running Claude blind is a choice. Most operators don't realize they're making it. With one session and one task, the terminal is your status display - you watch it scroll and know what's happening. Add a second session, a background worker, and a pipeline running overnight, and that view disappears. A worker stalls at 2 AM. Context fills to 80% on a long job and the session degrades without warning. A rate limit approaches, the queue keeps pushing, and the 429 hits mid-task. None of it was hidden from you. It just had nowhere to go. This book builds the display layer that surfaces all of it in real time. Two layers compose the system. First: a per-session statusline that reads from a hook-written state file, showing session cost, context saturation, token burn rate, and rate-limit headroom in a compact line. Hooks write the state on every tool call; the statusline reads and refreshes without blocking the session. Saturation becomes visible before it degrades performance. Burn rate becomes visible before a limit hits. Second: a system snapshot - a script that walks project directories, finds every worker, reads its last heartbeat, and classifies health as OK, IDLE, DORMANT, or BROKEN. IDLE means the worker missed its last two heartbeats. DORMANT means no state written in four hours. BROKEN means a failure marker exists. Each classification carries a meaning; 'running or not running' is too coarse for a fleet you're not watching. The snapshot runs on demand and on a thirty-second timer. Both layers feed a tmux layout with the whole picture on screen at once: current session's statusline, system snapshot refreshing on the timer, queue depth across all projects. The layout ships as a committed shell script - versioned, reproducible, owned by the codebase. Chapter by chapter, each component is built separately and explained at the seam where it connects to the others. The hook architecture comes first - what fires on PreToolUse, what fires on PostToolUse, and why the state file is the right boundary between session internals and external display. After that: statusline rendering, health classification with its threshold tuning, and a queue depth reader that counts pending tasks without touching files that workers own. The tmux layout chapter covers assembly, explains what belongs on a live display versus what belongs in a log, and ends with a complete worked session running the full fleet overnight so the reader can see what a real failure looks like when the HUD catches it. Before the HUD, you are operating on faith that nothing has stalled. After it, you have measurement. That gap is the difference between a pipeline that sometimes works and a system you can leave running.Written for developers who already run Claude Code across multiple projects and want real visibility into what their system is doing while they are not watching.…

Taschenbuch. Condition: Neu. Neuware - Claude handles triage and drafts inside a session. It stops when you close the window. This book keeps it running while you're away. Seven chapters, each one a working part of one machine: - the complete Claude Code hook lifecycle- a PreCompact baton that survives the context window getting cut- scheduled runners with real mutual exclusion and kill switches- folder watchers that handle race conditions and loop guards- a self-verifying pipeline whose hard gates stop bad output cold- the fail-open engineering that makes all of it safe to leave running overnight- a build-and-deploy step that closes the loop from source to shipped artifact>This is for advanced users who are comfortable in the Claude Code CLI.…

Taschenbuch. Condition: Neu. Neuware.

Taschenbuch. Condition: Neu. Neuware - You can get Claude to produce a draft in an afternoon. Drafting was never the hard part. What's hard is a manuscript that holds together and sounds like you wrote it, clears the bar a paying reader expects, and then gets done again for the next book and the one after that - at the same standard, every time. That takes a production line. A single lucky session can't give you repeatability. This book is that line, built from the author's real practice: nine stages, each one leaving a file on disk, each one gated before the next is allowed to start. You anchor the voice first, so every later stage has a fixed target to measure against. A three-agent council stress-tests the plan before any prose gets written. The draft comes out in versioned pieces, with a blocking fact-check and a voice-fidelity gate standing between draft and polish. Polish gets measured against four literary metrics - hapax score, Herdan's C, Flesch-Kincaid grade, lexical density - by a script that refuses to pass work still reading machine-made. The interior is built programmatically to KDP spec instead of hand-formatted in a word processor. A generated cover, composited from a locked style string, keeps the series coherent at thumbnail scale. Your listing draws its title, keywords, and categories from the outline and a sample chapter, so discoverability is earned instead of guessed at. Then the finished book is deployed and verified over HTTP - you confirm the live page is the thing you built. Every mechanism here is real: the gates that have blocked the author's own chapters, the spec that survived contact with KDP's interior validator, the cover compositor that stopped eating whole afternoons. You get the working technique, lifted straight from a line that ships. By the end, you have a pipeline you can point at the next book. The first run shows you where your line bends. Every run after is faster, because the bends are already fixed. This book is for advanced Claude Code users who are comfortable driving a multi-stage pipeline.…

Paperback. Condition: new. Paperback. Running Claude blind is a choice. Most operators don't realize they're making it. With one session and one task, the terminal is your status display - you watch it scroll and know what's happening. Add a second session, a background worker, and a pipeline running overnight, and that view disappears. A worker stalls at 2 AM. Context fills to 80% on a long job and the session degrades without warning. A rate limit approaches, the queue keeps pushing, and the 429 hits mid-task. None of it was hidden from you. It just had nowhere to go. This book builds the display layer that surfaces all of it in real time. Two layers compose the system. First: a per-session statusline that reads from a hook-written state file, showing session cost, context saturation, token burn rate, and rate-limit headroom in a compact line. Hooks write the state on every tool call; the statusline reads and refreshes without blocking the session. Saturation becomes visible before it degrades performance. Burn rate becomes visible before a limit hits. Second: a system snapshot - a script that walks project directories, finds every worker, reads its last heartbeat, and classifies health as OK, IDLE, DORMANT, or BROKEN. IDLE means the worker missed its last two heartbeats. DORMANT means no state written in four hours. BROKEN means a failure marker exists. Each classification carries a meaning; "running or not running" is too coarse for a fleet you're not watching. The snapshot runs on demand and on a thirty-second timer. Both layers feed a tmux layout with the whole picture on screen at once: current session's statusline, system snapshot refreshing on the timer, queue depth across all projects. The layout ships as a committed shell script - versioned, reproducible, owned by the codebase. Chapter by chapter, each component is built separately and explained at the seam where it connects to the others. The hook architecture comes first - what fires on PreToolUse, what fires on PostToolUse, and why the state file is the right boundary between session internals and external display. After that: statusline rendering, health classification with its threshold tuning, and a queue depth reader that counts pending tasks without touching files that workers own. The tmux layout chapter covers assembly, explains what belongs on a live display versus what belongs in a log, and ends with a complete worked session running the full fleet overnight so the reader can see what a real failure looks like when the HUD catches it. Before the HUD, you are operating on faith that nothing has stalled. After it, you have measurement. That gap is the difference between a pipeline that sometimes works and a system you can leave running.Written for developers who already run Claude Code across multiple projects and want real visibility into what their system is doing while they are not watching. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condition: new. Paperback. Claude handles triage and drafts inside a session. It stops when you close the window. This book keeps it running while you're away. Seven chapters, each one a working part of one machine: the complete Claude Code hook lifecyclea PreCompact baton that survives the context window getting cutscheduled runners with real mutual exclusion and kill switchesfolder watchers that handle race conditions and loop guardsa self-verifying pipeline whose hard gates stop bad output coldthe fail-open engineering that makes all of it safe to leave running overnighta build-and-deploy step that closes the loop from source to shipped artifactThese patterns come from systems I actually run. The runner skeletons are the real files - private paths swapped for generic ones, nothing else touched. Hook wiring is shown exactly as written. This is for advanced users who are comfortable in the Claude Code CLI. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…