Chapter 1: Introduction
Why there is a need to rethink software engineering, and what rewilding means in this context.
rewildingsoftware engineering
A book written in the open by Tudor Girba and Simon Wardley about how we make decisions, Moldable Development and all the derived implications in the AI era.
Chapter 2: How we make decisions
Why software engineering should be regarded primarily as a decision-making activity, and how doing so paves the way for making systems explainable. Shows a case study of how recovering a data lineage helped modernize a legacy system.
Chapter 3: Questions and answers
The role of questions and answers. Introduces time to answer (ttA) and time to question (ttQ). Shows how decreasing them leads to better decisions.
Chapter 4: Flexing those thinking muscles
The importance of both defined and dynamic explorations. Explained through a couple of distinct case studies.
Chapter 5: Different folks for different strokes
The inside of systems can be made explainable to non-technical people, too. And once systems become explainable, to vibe or not to vibe code is not the only choice.
Chapter 6: Myths we tell ourselves
Software is a domain of invisible knowledge work. It’s hard to see progress, quality or risks in the way that you can with building bridges. As a result myths flourish.