0 reviews
Chapters
6
Language
English
Genre
Published
July 4, 2025
Picking up where 'Ertugrul: Apparently, Destiny Called (Book 1)' left off, our hero and his surprisingly resilient tribe have survived the initial 'just don't die' phase of 13th-century Anatolia. Having navigated the treacherous waters of crumbling empires, opportunistic neighbors, and the general inconvenience of being a small fish in a very large, very violent pond, Ertugrul has managed to carve out a small corner for himself. But apparently, destiny wasn't done calling just yet. This second installment dives into the slightly more complex challenge of not just surviving, but *expanding*. This means dealing with the administrative headaches of actually *governing* territory, facing off against even larger, more annoyed superpowers (hello again, Byzantines and Mongols!), and navigating the ever-shifting sands of tribal and political allegiances – because apparently, success just makes things more complicated. 'Ertugrul: Apparently, Destiny Called Again' follows the Bey as he solidifies his gains, makes difficult choices that will shape the future of his lineage, and continues to prove that a determined group with sharp axes and an even sharper leader can punch significantly above their weight. Featuring more strategic maneuvering, higher stakes betrayals, and the continued, slightly exasperated question of 'Seriously, destiny *again*?', this book is for history enthusiasts who appreciate their historical narratives with a side of sardonic wit and the acknowledgment that building an empire is probably harder than deploying a Kubernetes cluster.
Inspired by what you've read? Turn your ideas into reality with FastRead's AI-powered book creation tool.
Start Writing NowGohar Younas Malik, who apparently didn't learn his lesson about sticking to Python and Docker after the first book, is back for more historical hijinks. Still a seasoned backend developer with over six years of experience wrestling complex systems using Python, Django, Docker, and a whole alphabet soup of AWS services, Gohar now apparently finds managing historical empires only *slightly* less chaotic than debugging asynchronous tasks with Celery and RabbitMQ. He assures us this book has fewer cascading failures than a bad microservice deployment. When not contemplating the strategic implications of historical alliances or database schemas, he's likely arguing about cricket or politics. This is his second attempt at convincing the world his historical insights are as robust as his scalable backend architectures.
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar
By Gohar