I never set out to be a CTO. In fact, I didn’t even have a computer science degree. But somewhere between firefighting server crashes at 3 a.m. and obsessing over replication lag graphs, I found myself building systems that would eventually power over a million online stores at Dukaan.
This book, The Accidental CTO, is my behind-the-scenes account of that journey. It’s not a dry academic manual filled with abstract diagrams. Instead, it’s a story-driven handbook — one that mixes late-night startup battles with the hard system design lessons that only come from being in the trenches.
From scaling a scrappy MVP to running massive distributed pipelines, I’ll take you through the challenges we faced and the decisions that made (or nearly broke) us.
I didn’t want to write another "theory of distributed systems" book. There are already plenty of those.
What I wanted to share is the practical side of system design — the part you only learn when a real company, with real customers and real money at stake, is on fire. The part where you’re not solving toy interview questions but dealing with:
This is the stuff no textbook teaches you.
Whether you’re a software engineer, architect, or startup founder, I wrote this book to help you see distributed systems not as academic puzzles, but as living, evolving machines that you can actually build, operate, and grow.
If you’ve ever wondered how real companies actually scale — not in theory, but in practice — this is my candid, first-hand story.
And maybe, just maybe, you’ll find a bit of yourself in The Accidental CTO.
$ claude mcp add The-Accidental-CTO \
-- python -m otcore.mcp_server <graph>