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.
As the narrative progresses, the line between the demon Hastar and the protagonist Vinayak blurs. The film asks a chilling question: Who is the real monster?
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Jesper Kyd’s atmospheric musical score combines traditional Indian instruments with dark, electronic undertones, building a sense of inescapable dread.
The original producers, Sohum Shah and Aanand L. Rai, struck a deal with Amazon Prime Video. The version available on Prime Video .
Do you need help finding it legally with subtitles?
You can also stream "Tumbbad" with English subtitles on Amazon Prime Video. Here's how:
Its legend grew even larger with a re-release in theaters in September 2024. The re-release was a phenomenal success, shattering previous box-office records for a re-run film and even surpassing the opening-day collections of classics like "Sholay" and "Mughal-e-Azam" in some regions. This resurgence cemented "Tumbbad" not just as a cult film, but as a mainstream phenomenon, proving that audiences crave bold, original, and terrifying cinema.
Depending on your region, Tumbbad may be available for digital rent or purchase.
It was the language that finally unlocked it.
If you prefer to rent or buy individual movies, you can find "Tumbbad" on YouTube Movies. Here's how:
The haunting background score by Jesper Kyd (known for his work on the Assassin's Creed video game series) combined with local Indian instrumentation creates an immersive, spine-chilling auditory experience. 4. A Metaphor for Human Nature
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.