All Books

A book series

The System Parables

A series about how software systems actually work, taught entirely through story.

Three books. 113 chapters. Not one line of code.

The three books of The System Parables: Beginnings at the Well, The Gaps We Carry and What the Masters Forget

Where it came from

I was born in Kerala, India. My father had many ventures, and one of them had Gurukulam in its name.

Gurukulam is an idea from ancient India, where a student learned directly from a teacher. I wanted to find out how easily the ideas behind the systems we all depend on could be understood if they were taught that way.

So I kept the teacher and the student, and changed the rest a little. The teaching is a conversation, and the people in it are characters I chose. An old Master who spent thirty years building these things before he came home sits beside a well in a village of fifty households. In the first book he teaches four people: a baker, a student, a man whose job no longer needs doing, and a teacher.

In these books people get the answer wrong before they get it right, and the wrong answer is usually the one you would have given. There is no code in any of them, and no tool, company or product is named. The things that change are not the things worth teaching.

It took me over two and a half years to finish the series.

The books, in order

Cover of Beginnings at the Well

The System Parables · Book 1 of 3

Beginnings at the Well

Thirty-five parables on how things get built

If you want to understand how systems actually work, not the code, the thing underneath it, this book teaches it through parables instead of manuals.

Nobody in the village was ever thirsty for water. They were thirsty for the morning it was costing them: the half day's walk, the barrels, the neighbour you had to ask and then remember asking.

Book details page
Cover of The Gaps We Carry

The System Parables · Book 2 of 3

The Gaps We Carry

Forty-two parables on how systems fail

Every app, website, bank and shop you use is a system, and every one of them fails sometimes. This book explains why, in plain language, through a story anyone can follow.

It shows why information goes out of date without anyone noticing, what happens when something turns slow instead of breaking, and why problems are so often found by a customer first. You do not need to be technical to read it.

Book details page
Cover of What the Masters Forget

The System Parables · Book 3 of 3

What the Masters Forget

Thirty-six parables on handing work on

Somebody on your team knows how a thing works and cannot explain it. When that person leaves, what they knew leaves with them, and writing it down beforehand almost never works. This book is about why.

It is for engineers, team leads and anyone who has inherited a system and a silence. There is no code in it, and no tool, company or product is named anywhere. You do not need to have read the first two books.

Book details page

Each book can be read on its own, so begin with the one that matches the problem you have.