ISBN: 9798181748804 - the new way to build software: practical agent orchestration and harnesses in 2026: 5 (ai and agentic engineering) (6 resultados)

Taschenbuch. Condición: Neu. Neuware - 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 team- What changed, in language you can brief a VP with- A plain definition of the new default you can put on a wall or a wiki- A map of the orchestration layer and a named owner for it- The verification culture, written as team norms instead of personal habits- The trust gradient: a dial you can read and widen as the work proves out- A 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.…

Paperback. Condición: 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.…

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

Condición: New. Print on Demand.

PAP. Condición: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condición: 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.…