0 reviews
Chapters
6
Language
English
Genre
Published
July 5, 2025
Picking up after the relative 'calm' of Ertugrul: Apparently, Destiny Called Again, where our hero managed to solidify his hold on a small corner of Anatolia, Book 3 dives headfirst into the inevitable consequences of not just surviving, but actually succeeding. Having dealt with the initial headaches of governance and batted away a few minor-league threats, Ertugrul now faces the true test: the established superpowers are *really* starting to pay attention. This installment sees the Bey navigating a treacherous landscape dominated by the waning Seljuk Sultanate of Rum, the ever-present shadow of the Mongol Ilkhanate, and the Byzantine Empire, who are frankly tired of this upstart Turk. But external threats are just the beginning; the narrative expands to introduce other prominent figures of the era – power players, rivals, and potential allies whose ambitions clash or align with Ertugrul's burgeoning vision, adding layers of political intrigue and tribal rivalries that make managing asynchronous tasks look like a walk in the park. 'Ertugrul: Apparently, Destiny Has Caller ID Issues' explores the delicate balance between consolidation and expansion, the brutal calculus of alliances and betrayals on a grander scale, and the sheer exhaustion of having destiny call you *again*, often at the least convenient times. It's about moving from a regional player to a force that major empires must reckon with, all while grappling with the internal politics of a growing beylic and the introduction of characters whose historical impact rivals Ertugrul's own. For history enthusiasts who appreciate the gritty, complicated reality of empire-building served with a side of 'are you kidding me?' sarcasm, this book proves that the higher you climb, the harder the fall – unless, of course, destiny decides to give you a push.
Inspired by what you've read? Turn your ideas into reality with FastRead's AI-powered book creation tool.
Start Writing NowGohar Younas Malik is back, still inexplicably writing about 13th-century Anatolia instead of optimizing database queries. A seasoned backend developer with over six years battling complex systems using Python, Django, Docker, and a formidable array of AWS services (EC2, S3, RDS, SQS, Redshift, you get the picture), Gohar continues to find managing historical political alliances only *slightly* less prone to unexpected failures than deploying a new microservice without proper testing. He's still convinced that Ertugrul's strategic maneuvering could benefit from a good caching layer. When not contemplating the historical equivalents of race conditions or arguing about cricket, politics, or current affairs, he's apparently trying to convince the world that his historical insights are as robust as his scalable backend architectures. He remains open to remote or relocation opportunities, presumably to escape the relentless calls of historical destiny.
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