liveBook · Manning

What you will learn in Decision Engineering

Making architecture and technology choices that last

by Grygoriy Gonchar · Manning Early Access Program (MEAP)

Chapter by chapter

Chapter 1: Understanding technical decisions

The introduction explains why consequential technical choices require decision-making skill beyond software-building expertise, especially as AI speeds up coding.

1.1 What is “good” decision-making? · 1.1.1 Even good decisions come with uncertainty · 1.1.2 Decisions that deserve thinking · 1.1.3 Decision-making as its own discipline · 1.2 Why decision making is a critical engineering skill · 1.2.1 The cost of poor decisions · 1.2.2 How decisions change in the age of AI · 1.3 The decision lifecycle · 1.3.1 Phase 1: Framing the decision · 1.3.2 Phase 2: Evaluating and choosing options · 1.3.3 Phase 3: Making the decision stick · 1.4 Scope and the road ahead · 1.5 Summary

What you learn in chapter 1 →

Chapter 2: Understanding the problem

The chapter introduction explains why engineers must understand the problem and its business context before choosing a technical solution.

2.1 Problem definition beyond requirements · 2.1.1 From quick solutions to the real needs · 2.1.2 How engineering shapes the requirements · 2.1.3 Architecturally significant requirements · 2.2 Thinking in service tiers · 2.2.1 Availability · 2.2.2 Durability · 2.2.3 Latency · 2.2.4 Load · 2.2.5 Volatility · 2.2.6 Comparing service tiers · 2.3 Compliance requirements · 2.3.1 Separating requirements from controls · 2.3.2 Legal requirements · 2.3.3 Security requirements · 2.3.4 Common tips for addressing compliance requirements · 2.3.5 What about architecture requirements? · 2.4 When the problem is ready for solution discussion · 2.5 Summary

What you learn in chapter 2 →

Chapter 3: Reading the context

This introduction explains why requirements alone do not determine the right technical choice and identifies the system, team, and company contexts that also shape it.

3.1 System context · 3.1.1 The 5W questions · 3.1.2 What exists in the system today? · 3.1.3 Where is the component used? · 3.1.4 When was it built? · 3.1.5 Why is it the way it is? · 3.1.6 Who owns it, who knows it deeply, and who has the historical context? · 3.1.7 Understanding whether your findings are solid enough · 3.2 Team context · 3.2.1 Team knowledge · 3.2.2 Talent availability · 3.2.3 On-call setup · 3.2.4 Team preferences · 3.2.5 Understanding which forces are binding · 3.3 Company context · 3.3.1 Business strategy · 3.3.2 Technology strategy · 3.3.3 Company scale · 3.3.4 Industry norms · 3.4 Reading context: a worked example · 3.5 Summary

What you learn in chapter 3 →

Chapter 4: Evaluating external technologies

The introduction explains why adopting external technology deserves a deliberate decision grounded in the organization’s needs and proportionate to the commitment.

4.1 Qualifying candidates · 4.1.1 Candidates sourcing · 4.1.2 Screening against key requirements · 4.2 Running closer evaluation · 4.2.1 Voice of Developer analysis · 4.2.2 Learning directly from people been there · 4.2.3 Getting own first hand experience · 4.3 Open-source technologies evaluation · 4.3.1 Assessing usage and popularity · 4.3.2 Community health and maintainability signals · 4.3.3 Understanding limitations of the free version · 4.3.4 Understanding licences · 4.3.5 Calibrating for ecosystem differences · 4.4 Commercial solutions evaluation · 4.4.1 Dealing with limited information · 4.4.2 Pricing and negotiation dynamics · 4.4.3 Including runner-up products · 4.4.4 Assessing product continuity risks · 4.4.5 What switching to a different technology could cost us · 4.4.6 Evaluating contract conditions · 4.4.7 Running the tracks in parallel · 4.5 Summary

What you learn in chapter 4 →

Concepts explained in this book

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.