By Gergely Orosz, the author of The Pragmatic Engineer Newsletter and Building Mobile Apps at Scale
Navigating senior, tech lead, staff and principal positions at tech companies and startups. An Amazon #1 Best Seller. New: the hardcover is out! As is the audibook. Now available in 6 languages.
K. Ali's perspectives on Indo-Pak relations offer a fresh understanding of the complex dynamics between the two nations. By challenging the dominant narrative and highlighting the significance of social, cultural, and economic ties, Ali's work provides a foundation for a new history of Indo-Pak relations. This paper argues that a new history of Indo-Pak relations, informed by Ali's perspectives, can help to nuance our understanding of the complex interactions between India and Pakistan, ultimately contributing to a more informed and empathetic approach to the relationship.
This paper argues that K. Ali's perspectives on Indo-Pak relations offer a nuanced understanding of the complex dynamics between the two nations, highlighting the need for a new history that incorporates diverse experiences, voices, and perspectives.
The India-Pakistan relationship has been a complex and contentious issue since the two nations gained independence in 1947. The existing historical narrative on Indo-Pak relations has been shaped by various factors, including colonial legacy, partition, and ongoing conflicts over Kashmir and other territorial disputes. This paper aims to explore the perspectives of historian K. Ali on Indo-Pak relations and present a new history of the complex dynamics between the two nations.
A New History of Indo-Pak Relations: A Critical Analysis of K. Ali's Perspectives
K. Ali, a prominent historian, has written extensively on South Asian history, including the India-Pakistan relationship. His work challenges the dominant narratives on the subject, offering fresh insights into the complex interactions between India and Pakistan. Ali's perspectives on Indo-Pak relations emphasize the need to move beyond the traditional focus on conflict and instead examine the social, cultural, and economic ties that have shaped the relationship.
The book is separated into six standalone parts, each part covering several chapters:
Parts 1 and 6 apply to all engineering levels: from entry-level software developers to principal or above engineers. Parts 2, 3, 4 and 5 cover increasingly senior engineering levels. These four parts group topics in chapters – such as ones on software engineering, collaboration, getting things done, and so on.
This book is more of a reference book that you can refer back to, as you grow in your career. I suggest skimming over the career levels and chapters that you are familiar with, and focus reading on topics you struggle with, or career levels where you are aiming to get to. Keep in mind that expectations can vary greatly between companies.
In this book, I’ve aimed to align the topics and leveling definitions closer to what is typical at Big Tech and scaleups: but you might find some of the topics relevant for lower career levels in later chapters. For example, we cover logging, montiroing and oncall in Part 5: “Reliable software systems” in-depth: but it’s useful – and oftentimes necessary! – to know about these practices below the staff engineer levels.
The Software Engineer's Guidebook is available in multiple languages:
You should now be able to ask your local book shops to order the book for you via Ingram Spark Print-on-demand - using the ISBN code 9789083381824. I'm also working on making the paperback more accessible in additional regions, including translated versions. Please share details here if you're unable to get the book in your country and I'll aim to remedy the situation.
I'd like to think so! The book can help you get ideas on how to help software engineers on your team grow. And if you are a hands-on engineering manager (which I hope you might be!) then you can apply the topics yourself! I wrote more about staying hands-on as an engineering manager or lead in The Pragmatic Engineer Newsletter.
I've gotten this variation of a question from Data Engineers, ML Engineers, designers and SREs. See the more detailed table of contents and the "Look inside" sample to get a better idea of the contents of the book. I have written this book with software engineers as the target group, and the bulk of the book applies for them. Part 1 is more generally applicable career advice: but that's still smaller subset of the book.