Browse the book & resources
Simple ink sketch of stones and a small cairn marking a trail beneath pinesIllustration based on the author’s trail photograph

A book in progress

Trail Markers

Choosing Where AI Fits in Engineering

Choose where AI creates value, where it does not, and how to tell the difference.

Start reading →

This is a compact first draft of a longer book, not an approved publication. Its case material comes from identified published sources; the seven files in book/interview/ are desk research, not interviews conducted with practitioners for this book. The original interviews required by the drafting plan have not happened. Treat the questions and exercises as proposals, not findings about your organization. Numerical claims describe their cited settings; they are not promises about yours.

A note to the reader

You have probably been asked to make an AI decision with too little time and too much certainty in the room. Somebody has a demo, a spending proposal, a report about time saved, or a chart of code generated. None of these is a bad place to begin. None tells you whether customers received something useful, the company recovered its investment, the team can sustain the new workload, or an engineer still has room to learn and say no.

This book is for the person who must make that decision, and for the people who will live with it. It offers no universal ranking of tools and no target for the percentage of work that should involve AI. It offers a route: name the outcome and the people affected; find the actual constraint; compare an AI intervention with a credible non-AI option; set boundaries proportionate to harm; measure what happened; then keep, change, expand, or stop. When you lack a comparison, say so. When a result disappoints, learn from it rather than hiding it.

The nine competencies of an engineering organization provide a map, not a compulsory itinerary. Effective, efficient, innovative, and engaging are the goals in the competency guide; this book also makes reliability explicit so that a faster trip cannot be mistaken for a safe one. The four perspectives on value—customer, company, team, individual—tell us who arrived, who paid, and who may have been left behind.

How to use this draft

Read Part I for the decision lens, Part II for the constraint you actually face, and Part III for a pilot and measurement method. Part IV turns the method into a next-quarter choice. Chapter endings are prompts for discussion, not scores for judging individual engineers. Citations point to primary studies or named organizational accounts when available. A field experiment about completed tasks, a vendor's financial model, an employee's account, and an incident report are different kinds of evidence. The book will keep saying which is which because the decisions deserve that honesty.

Editorial status: All 20 chapters are provisional short-form drafts. Original reporting, deep chapter expansion, cross-chapter editing, expert checking, and author approval remain open.

About the author

Baiyun (Ben) Gao is an engineering practitioner with more than 20 years of professional experience in software engineering, enterprise architecture, cloud platforms, AI, and secure SaaS solutions. TOGAF-certified, he has led solution engineering and delivery across government, aerospace and defense, cybersecurity, satellite communications, broadcasting, and enterprise technology sectors. He focuses on translating architecture into measurable business value through scalable platforms, modernized delivery practices, and customer-centered innovation.