Items related to The Business Engineer: From Writing Code to Owning...
The Business Engineer: From Writing Code to Owning the Outcomes (The Enterprise Intelligence Series) - Softcover
Book 3 of 5: The Enterprise Intelligence Series
Synopsis
Agents did not take engineering away from us. They exposed how much of engineering was never engineering.
Kabir Anand becomes an engineer because of a bridge. His father inspected railway bridges for thirty-one years and told him once: a train crosses because a man put his name on a number.
Kabir spends the next twenty years learning the opposite lesson. Pune, 2006, where a signed requirement document is scripture. A batch job that runs twice and debits four thousand customers. Bangalore, distributed systems, a growing reputation. Then Dubai, and eighteen months building the finest platform of his career, killed in a six-minute strategy review because nobody in the room, including him, had ever asked what the capability earned.
Then a Thursday afternoon in 2024. He hands an AI agent a brief he had estimated at six weeks. By five that evening the machine has written, unprompted, the six lines of code whose absence had cost him that night in 2008.
It has not taken my job. It has taken my alibi.
THE BUSINESS ENGINEER follows one engineer from Software 1.0 to Software 3.0, from writing code to owning outcomes, and eventually out of the building entirely into a company that sells cleared shipments instead of software. It is a novel, and it is a working manual.
Inside, illustrated with 46 original diagrams:- The three-layer model: Intent and Assurance stay human, Orchestration is shared with machines
- The gate: why a capability needing 40 implementers needs 8 outcome owners, and what happens to the other 32
- The Authority Clause: the four rights that must be granted in writing, or the title is a liability transfer
- Why architecture is now a pricing decision, and what a twelvefold cost spread on one outcome looks like
- Impostor syndrome as an evidence problem rather than a character problem, and the five moves that close the gap
- Twelve mental models and ten principles, extracted for reuse
- Where the senior engineers of 2036 come from, a question this book refuses to pretend is solved
For software engineers, staff and principal engineers, engineering managers, CTOs, CIOs, and product leaders who suspect the ground has moved and want a map drawn by someone who was standing on it.
Written in Dubai, the book takes its closing discipline from the city's own philosophy: say what you will do, do it, prove it, sign it.
A work of fiction. The narrator, his colleagues, and every company in these pages are invented. Financial figures are illustrative and labelled as such in the Author's Note.
"synopsis" may belong to another edition of this title.
Search results for The Business Engineer: From Writing Code to Owning...
Stock Image
The Business Engineer: From Writing Code to Owning the Outcomes (The Enterprise Intelligence Series)
Print on DemandSeller: California Books, Miami, FL, U.S.A.
Seller rating 5 out of 5 stars
Condition: New. Print on Demand. Seller Inventory # I-9798193479468
Stock Image
The Business Engineer
Seller: PBShop.store UK, Fairford, GLOS, United Kingdom
Seller rating 5 out of 5 stars
PAP. Condition: New. New Book. Shipped from UK. Established seller since 2000. Seller Inventory # L2-9798193479468
Buy New
US$ 42.73
US$ 5.50 shipping
Ships from United Kingdom to U.S.A.
Ships from United Kingdom to U.S.A.
Quantity: Over 20 available
Stock Image
The Business Engineer (Paperback)
Print on DemandSeller: CitiRetail, Stevenage, United Kingdom
Seller rating 5 out of 5 stars
Paperback. Condition: new. Paperback. Agents did not take engineering away from us. They exposed how much of engineering was never engineering.Kabir Anand becomes an engineer because of a bridge. His father inspected railway bridges for thirty-one years and told him once: a train crosses because a man put his name on a number.Kabir spends the next twenty years learning the opposite lesson. Pune, 2006, where a signed requirement document is scripture. A batch job that runs twice and debits four thousand customers. Bangalore, distributed systems, a growing reputation. Then Dubai, and eighteen months building the finest platform of his career, killed in a six-minute strategy review because nobody in the room, including him, had ever asked what the capability earned.Then a Thursday afternoon in 2024. He hands an AI agent a brief he had estimated at six weeks. By five that evening the machine has written, unprompted, the six lines of code whose absence had cost him that night in 2008.It has not taken my job. It has taken my alibi.THE BUSINESS ENGINEER follows one engineer from Software 1.0 to Software 3.0, from writing code to owning outcomes, and eventually out of the building entirely into a company that sells cleared shipments instead of software. It is a novel, and it is a working manual.Inside, illustrated with 46 original diagrams: The three-layer model: Intent and Assurance stay human, Orchestration is shared with machinesThe gate: why a capability needing 40 implementers needs 8 outcome owners, and what happens to the other 32The Authority Clause: the four rights that must be granted in writing, or the title is a liability transferWhy architecture is now a pricing decision, and what a twelvefold cost spread on one outcome looks likeImpostor syndrome as an evidence problem rather than a character problem, and the five moves that close the gapTwelve mental models and ten principles, extracted for reuseWhere the senior engineers of 2036 come from, a question this book refuses to pretend is solvedFor software engineers, staff and principal engineers, engineering managers, CTOs, CIOs, and product leaders who suspect the ground has moved and want a map drawn by someone who was standing on it.Written in Dubai, the book takes its closing discipline from the city's own philosophy: say what you will do, do it, prove it, sign it.A work of fiction. The narrator, his colleagues, and every company in these pages are invented. Financial figures are illustrative and labelled as such in the Author's Note. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Seller Inventory # 9798193479468
Buy New
US$ 48.35
US$ 48.95 shipping
Ships from United Kingdom to U.S.A.
Ships from United Kingdom to U.S.A.
Quantity: 1 available
Stock Image
The Business Engineer : From Writing Code to Owning the Outcomes
Published by
Amazon Digital Services LLC - Kdp Aug 2026, 2026
ISBN 13: 9798193479468
New
Taschenbuch
Seller: AHA-BUCH GmbH, Einbeck, Germany
Seller rating 5 out of 5 stars
Taschenbuch. Condition: Neu. Neuware - Agents did not take engineering away from us. They exposed how much of engineering was never engineering.Kabir Anand becomes an engineer because of a bridge. His father inspected railway bridges for thirty-one years and told him once: a train crosses because a man put his name on a number.Kabir spends the next twenty years learning the opposite lesson. Pune, 2006, where a signed requirement document is scripture. A batch job that runs twice and debits four thousand customers. Bangalore, distributed systems, a growing reputation. Then Dubai, and eighteen months building the finest platform of his career, killed in a six-minute strategy review because nobody in the room, including him, had ever asked what the capability earned.Then a Thursday afternoon in 2024. He hands an AI agent a brief he had estimated at six weeks. By five that evening the machine has written, unprompted, the six lines of code whose absence had cost him that night in 2008.It has not taken my job. It has taken my alibi.THE BUSINESS ENGINEER follows one engineer from Software 1.0 to Software 3.0, from writing code to owning outcomes, and eventually out of the building entirely into a company that sells cleared shipments instead of software. It is a novel, and it is a working manual.Inside, illustrated with 46 original diagrams: - The three-layer model: Intent and Assurance stay human, Orchestration is shared with machines- The gate: why a capability needing 40 implementers needs 8 outcome owners, and what happens to the other 32- The Authority Clause: the four rights that must be granted in writing, or the title is a liability transfer- Why architecture is now a pricing decision, and what a twelvefold cost spread on one outcome looks like- Impostor syndrome as an evidence problem rather than a character problem, and the five moves that close the gap- Twelve mental models and ten principles, extracted for reuse- Where the senior engineers of 2036 come from, a question this book refuses to pretend is solvedFor software engineers, staff and principal engineers, engineering managers, CTOs, CIOs, and product leaders who suspect the ground has moved and want a map drawn by someone who was standing on it.Written in Dubai, the book takes its closing discipline from the city's own philosophy: say what you will do, do it, prove it, sign it.A work of fiction. The narrator, his colleagues, and every company in these pages are invented. Financial figures are illustrative and labelled as such in the Author's Note. Seller Inventory # 9798193479468
Buy New
US$ 57.93
US$ 39.69 shipping
Ships from Germany to U.S.A.
Ships from Germany to U.S.A.
Quantity: 2 available