Halloran wes (20 risultati)

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. Established seller since 2000.

Paperback. Condizione: new. Paperback. The agent said "Done." You opened the app. It was broken.You are a competent developer. You can smell a bug from across the room. So why does AI pair programming feel like babysitting a confident intern who reports success it never checked? It is not your prompt engineering. Nobody defined what done meant, so the agent got to declare the word instead of earning it.That checkmark over broken work is the green lie, and it is why "done" is the most expensive sentence in agentic coding. It is why you still read every token instead of walking away, why vibe coding runs out of road the moment the work matters, and why good developers quietly downgrade an autonomous coding agent to faster autocomplete.Claude Code in Action is about making the agent earn the word. You hand it a definition of done it cannot fake, wrap that in a goal loop that refuses to stop until the work is actually green, and build a harness around it so autonomy is productive instead of dangerous. The fix is a loop, not a vibe, and every workflow in these pages was run against the real tool before it was written down.The working developer's method for agentic AI software engineering: The definition of done: a completion test the agent has to satisfy, so "done" stops being a lie.The goal loop: goal, completion test, cycle until green, for any task you hand off.The harness: project memory, a custom command, a verification step, and scoped permissions, built on a real repo.The fan-out: independent work sent to parallel subagents, with the results merged back clean.The weekend ship: one real product, idea to running software, in a single weekend.Read it and you will hand off work you do not have to re-read, catch the green lie before you act on it, and ship a real product over one weekend, the way the people you assumed were lying actually do it.For developers who can already code and are a few weeks into using a coding agent seriously. You have watched it break something with complete confidence, and maybe lost a Saturday to the revert. Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

Paperback. Condizione: new. Paperback. The everything app is the best idea you will ever fail to ship.Week three. Forty half-built features. Nobody has seen a single one. The idea was exciting for exactly one reason: it does everything. And that reason is the wall between you and a real product with a real user. You do not have a motivation problem. You have a scope problem wearing a motivation costume.Here is the trade at the center of it: an idea that does everything ships nothing, and a slice that does one thing ships Tuesday. Vibe coding with AI agents makes the labor cheap. It does not make the scope smaller. The whole job is learning to cut that slice without giving up the idea, and almost none of it is about code.The Everything App You Can Build takes the costume off. With an AI agent doing the labor and you supplying the judgment, you take one ambitious, multi-purpose app from a one-line idea to a deployed v1 that a real person uses and pays for. The everything app stays. It just becomes the destination instead of the first commit.What you build, one earned slice at a time: The one-week wedge: the smallest slice of your giant idea that ships in seven days and is still worth using.The build harness: a project memory file, a daily build session, and a verification step that stops the agent shipping confident wreckage.The scope ratchet: the rule that grows the app by earned slices and never rolls back into sprawl.The first-dollar test: the smallest honest way to charge, and the first dollar in the account.The launch loop: launching as a repeatable cycle, not a one-shot gamble.Read it and you will ship a software product solo instead of stalling at week three, deploy and monetize an app that started as a one-line idea, and keep the giant version alive as the destination your shipped slices are building toward.For the indie hacker with a side project graveyard, the solopreneur shipping a SaaS MVP, and the internal tools dev whose work a whole team quietly depends on. You can already ship small things. The big one is what keeps stalling. Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condizione: new. Paperback. Two engineers, one job. One spent the week typing. The other spent it deciding. They shipped the same feature by Friday, and the difference was not talent.The difference was that one of them builds software the way it gets built now, and the other had not noticed it changed. Nobody sent a memo. Agent orchestration, harnesses, and autonomous coding agents quietly stopped being the advanced move and became the floor, one team at a time. Most leaders are still treating that as a personal preference, settled engineer by engineer.The New Way to Build Software is for the person who has to make the call for a whole team. There is no prompt pack here and no manifesto. It is a working account of what actually changed, and a plan for moving a real team onto the new default without betting the quarter on a vibe.Modern AI developer tools are not the hard part, and every LLM coding assistant workflow looks fine in a demo. Teams stall on the same two questions afterward: who owns the harness, and how far do you let the agent run. Answering them for everyone else is engineering leadership work, and this book treats AI adoption as exactly that kind of decision.The working playbook for agentic engineering for teams, built from parts you can name and assign: The new default: a plain definition of how software gets built now, ready to put on a wall or a wiki.The orchestration layer: a map of the layer where context engineering for developers actually lives, with a named owner for it.The verification culture: checking the work, written as team norms instead of personal habits.The trust gradient: a dial for how far agents run, one you can read and widen as the work proves out.The 90-day adoption plan: one team moved onto the new way, with the first two weeks laid out day by day.Read it and you will explain what changed in language you can brief a VP with, put a named owner on your orchestration layer, and widen agent autonomy as the work proves out instead of as the hype demands.For senior engineers, tech leads, and engineering managers who can already ship and now have to decide how everyone else builds. If the AI transformation of your team is yours to lead, this book was written for you. Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condizione: new. Paperback. Everyone in the room saw the agent work. That is the problem.In production it fails one run in twelve, never the same way twice, and you carry the pager. You are not stuck because the agent cannot do the work. You watched it do the work. You are stuck because doing it once, on stage, with you watching is the easy part, and doing it every time, while you sleep, is the job nobody named for you.Harness Engineering names that gap: the demo cliff, and the climb back up. This is not a book about building an agent. You already built one. This is the book about making it deliver: the evals, verification, guardrails, observability, and recovery that turn an impressive toy into a production LLM application you would put your name on the pager for.The engineer's toolkit for reliable AI agents that actually deliver: Reliability as a number: a success rate against a fixed task set, tracked run over run, so better is a measurement instead of a feeling.The eval gate: agent evals run like CI, blocking a bad change before it ships.The verification wall: cheap checks first, expensive ones behind them, catching wrong output before a user ever does.The recovery path for the failures you cannot prevent: retry with judgment, fall back, escalate, roll back.Run records: LLM observability and monitoring that capture what the agent actually did, so a bad run is a query instead of an archaeology dig.The reliability budget for one real agent: a target you can defend and the guardrails that hold it.Read it and you will measure your agent instead of demoing it, ship changes behind an eval gate, catch wrong answers before your users do, and answer the 3 AM page with a query instead of a guess. A reliable agent still fails. Its failures are rare, cheap, caught before the user, and survivable when they are not. That is software reliability engineering, the discipline SRE brought to servers, applied to agents. This book is the engineering.For software, ML, and platform engineers who already run agentic loops and now own one in production. Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condizione: new. Paperback. The agent said "Done." You opened the app. It was broken. Nobody had told it what done meant.You are a competent developer. You can smell a bug from across the room. So why does working with an agent feel like babysitting a confident intern who reports success it never checked? It is not your prompting. "Done" was never defined, so the agent got to declare it instead of earning it. This book is about making it earn the word."Done" is the most expensive sentence in agentic coding. The checkmark over broken work is the green lie. It is why you still read every token instead of walking away, and why good developers quietly downgrade a powerful agent to faster autocomplete.The fix is a loop, not a vibe. You hand the agent a definition of done it cannot fake and wrap it in a goal loop that refuses to stop until the work is actually green. Around it you build a harness, so autonomy is productive rather than dangerous. Then you ship a real product over one weekend, the way the people you assumed were lying actually do it.What you buildA definition of done the agent has to satisfy, so "done" stops being a lieA goal loop for any task: goal, completion test, cycle until greenA harness on a real repo: project memory, one custom command, one verification step, scoped permissionsA fan-out that sends independent work to parallel subagents and merges the resultsOne shipped product, idea to running software, in a single weekendWho it is forDevelopers who can already code and are a few weeks into using an agent seriously. You have watched it break something with complete confidence, and maybe lost a Saturday to the revert. If you have ever believed a green checkmark for four seconds and then opened the app, this book was written for you.About the authorWes Halloran writes practical books for working developers and indie builders in the shift to AI-agent development. He works by the rule he teaches: never accept a green light you did not check. Every workflow in these pages was run against the real tool before it was written down, because a book about the green lie could not honestly be built any other way.Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Paperback. Condizione: new. Paperback. Week three. Forty half-built features. Nobody has seen a single one. The everything app is the best idea you will ever fail to ship.It is exciting for exactly one reason: it does everything. And that reason is the wall between you and a real product with a real user. I have watched a lot of strong builders stall right here. You do not have a motivation problem. You have a scope problem wearing a motivation costume, and this book takes the costume off.Here is the trade at the center of it: an idea that does everything ships nothing, and a slice that does one thing ships Tuesday. The whole job is learning to cut that slice without giving up the idea. Almost none of it is about code.With an AI agent doing the labor and you supplying the judgment, you take one ambitious, multi-purpose app from a one-line idea to a deployed v1 that a real person uses and pays for. The everything app stays. It just becomes the destination instead of the first commit.What you buildThe one-week wedge: the smallest slice of your giant idea that ships in seven days and is still worth using.The build harness: a project memory file, a daily build session, and a verification step that stops the agent shipping confident wreckage.The scope ratchet: the rule that grows the app by earned slices and never rolls back into sprawl.The first-dollar test: the smallest honest way to charge, and the first dollar in the account.The launch loop: launching as a repeatable cycle, not a one-shot gamble.Who it is forYou can already ship small things. The big one is what keeps stalling. Maybe you are an indie hacker, maybe you build the internal tools a whole team quietly depends on. Either way you have a repo graveyard and one idea you cannot let go of. That idea is why this book exists.About the authorWes Halloran writes practical books for working developers and indie builders making the shift to AI-agent development. No hype, only real tool behavior and workflows he has verified himself, because a green light you did not check does not count. He keeps his own repo graveyard, which is why this book goes after scope before anything else.Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Paperback. Condizione: new. Paperback. Everyone in the room saw the agent work. That is the problem. In production it fails one run in twelve, and you carry the pager.You are not stuck because the agent cannot do the work. You watched it do the work. You are stuck because doing it once, on stage, with you watching is the easy part, and doing it every time, while you sleep, is the job nobody named for you. This book names it: the demo cliff. Harness Engineering is the climb back up.You already built an agent. This book is about making it deliver. Evals, verification, guardrails, observability, recovery: the scaffolding that turns an impressive toy into a system you would put your name on the pager for.A reliable agent still fails. Its failures are rare, cheap, caught before the user, and survivable when they are not. That is engineering, and this book is the engineering.What you buildReliability as a number: a success rate against a fixed task set, tracked run over run.An eval gate that blocks a bad change before it ships, run like CI.A verification wall that catches wrong output before a user does, cheap checks first, expensive ones behind them.A recovery path for the failures you cannot prevent: retry with judgment, fall back, escalate, roll back.Run records of what the agent actually did, so a bad run is a query instead of an archaeology dig.A reliability budget for one real agent: a target you can defend and the guardrails that hold it.Who it is forSoftware, ML, and platform engineers who already run agentic loops and now own one in production. You shipped the feature, the demo recording is still in the channel, and the 3 AM page lands on you. If that is your week, this is your book.About the authorWes Halloran writes practical books for working developers and engineering leaders in the shift to AI-agent development. He has shipped agents that failed in ways no demo hinted at, so this book trusts measured runs over impressive ones. He works from real tool behavior and verified workflows, and never accepts a green light he did not check.Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. …

Paperback. Condizione: new. Paperback. Two engineers, one job. One spent the week typing. The other spent it deciding. They shipped the same feature by Friday, and the difference was not talent.The difference was that one of them builds software the way it gets built now, and the other had not noticed it changed. Nobody sent a memo. Agent orchestration and harnesses just stopped being the advanced move and became the floor, quietly, one team at a time. Most leaders are still treating that as a personal preference, settled engineer by engineer.I wrote The New Way to Build Software for the person who has to make the call for a whole team. There is no prompt pack here and no manifesto. It is a working account of what actually changed, and a plan for moving a real team onto the new default without betting the quarter on a vibe.What you take back to your teamWhat changed, in language you can brief a VP withA plain definition of the new default you can put on a wall or a wikiA map of the orchestration layer and a named owner for itThe verification culture, written as team norms instead of personal habitsThe trust gradient: a dial you can read and widen as the work proves outA 90-day adoption plan for one team, with the first two weeks laid out day by dayWho it is forSenior engineers, tech leads, and engineering managers who can already ship and now have to decide how everyone else builds. If you are the one who has to stand in front of the team and say this is how we build now, I wrote this for you.About the authorWes Halloran writes practical books for working developers and engineering leaders making the shift to AI-agent development. He writes about how the tools actually behave once the demo ends, and he does not accept a green light he did not check. This book comes out of watching team after team stall on the same two questions: who owns the harness, and how far do you let the agent run.Part of the AI and Agentic Engineering series. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…