Skip to main content

Suheldev - Analyzing the change in Amish Tripathi's writing

I have always been a fan of Amish Tripathi's books. All of them. Over the years, a lot has changed, which also includes his writing style. Well, that's just one man's perspective.

Here are the key distinctions of Suheldev from Amish Tripathi's other books:


I have been noticing a gradual change in Amish's writing which is eventually inclining to a cinematic perspective. And Suheldev justifies it the most. Certain sequences in the book are written in such a way that when you read them, it'll seem as if you're watching a movie. They could be fight sequences, or conspiracy sequences, anything. When we read, we form a picture. And that picture may seem relatable to the countless movies we have watched that have action and politics as their genres. To be honest and fair, if I look back at the first novels of Amish, The Shiva Trilogy, it wasn't cinematic, wasn't like watching any movie. It was a completely different world! Reading those novels felt like getting teleported into another body in a different place. So did Ram - Scion of Ikshvaku and Sita - Warrior of Mithila. I felt a bit of cinematic writing evident in the book Raavan - Enemy of Aryavarta, but the story was too impeccable to relate it with the established cinematic storylines or sequences. Mind you, I'm not saying that Suheldev's storyline or sequences are bad. They are amazing, the flow of Amish's writing is still there where you're not reading his book, you're watching it. But I just didn't feel as gripped or sucked into the world of Suheldev or the Turk-tormented Indians as I have with his earlier novels. Overall though, still an amazing book.

Least modified storyline

This time, Amish has picked up a historic character that very, very few people know about. As a student who has always loved history classes during his school days (yeah, I'm kind of a nerd), I can personally verify that we had never even heard, let alone were taught about these characters and wars. All we were taught about were the annexations by the Turks, the names of the rulers and certain names of the kingdoms that were rich at the time. So yes, making Indians aware of their own history is one extremely important credit that must be given to this novel. It's one thing to better your novel with edgy storylines and another to make people aware of the true legend. And Amish took the responsibility for both the tasks and finished them up respectfully. So the commendable act is to first pick a historic character who was not that known to Indians in the first place and write a fantasy fiction novel on his biography without hardly changing the storyline. Yes, he did modify the Maqsud-Masud character existence, but compare that to the modifications to the widely established and narrated stories of Lord Shiva and Lord Ram, his novel stories seem very humanly and amazingly legendary at the same time.

In conclusion, I would say that I enjoyed reading Suheldev, and I'm happy that it was a different book, a deviation from his Ram Chandra Series. Now all I'm waiting for is the war between Ram and Raavan and how Amish makes the role of Sita much more important in his novel!
Jai Maa Bhaarati!


Popular posts from this blog

Namaste JavaScript Quick Notes

Note:  Akshay Saini's Namaste JavaScript is probably the best course for JavaScript developers out there. These are my personal notes that I made while watching the course; they serve more of as an online quick reference for my understanding and revision, and I hope it benefits anyone reading it too! Everything in JS happens inside an Execution Context. Before a JS code is run, memory is allocated and variables are set as undefined   , and functions are set as their exact code in the scope within the Execution Context. The global execution context hosts all the global variables and function definitions. An Execution Context has 2 components: Memory, that stores variables and functions; and Code, that reads and executes the code. Call Stack maintains the order of execution contexts. Since JS is single threaded and asynchronous, at one point of time, only one function is executed which is at the top of the call stack. For each function, an execution context is created before executi

i3wm essentials - I (Brightness)

So you have started using i3 and somehow managed to open your browser and almost resumed your normal work.  But wait, the brightness is too much isn't it? Or is it too low? The mousepad used to work fine, but now all of a sudden tapping does not equal click?!  Don't worry.  This blog series will tell you all about the essential setup commands and common shortcuts that I use to navigate my work in i3, and how you can too. Changing the brightness So you just started i3 and you just can't take this brightness setting. You go for your function keys, and damn! They aren't working. Quick fix: Run the following command if you need to change the brightness ASAP. xrandr -q | grep ' connected' | head -n 1 | cut -d ' ' -f1 This will give an ouput that's the name of your monitor.  Use that monitor name here and change the values of brightness to suit your needs. xrandr --output <monitor-name> --brightness 0.7 Now that your eyes are comfortable, let me show

i3wm essentials - II

Welcome back! Let's continue this guide with other setup essentials for i3. Enabling Mousetap Chances are that if you're using a laptop, then tapping on the mousepad does not equal a click for you. You need to enable tapping in your config. Fortunately, there is one documentation available that works for majority of the setups. I don't need to explain this one in detail. Here you go: Enable tap to click in i3 . Volume Control This one is simple again. Do you remember the i3 config file I talked about in the previous blog ? All you need to do is go to that file and find the line: bindsym XF86AudioRaiseVolume Just below that line you will find lines with XF86AudioLowerVolume and XF86AudioMute too. Anyway, the truth is, there are 2 sets of lines with these keywords. Chances are that the line: bindsym XF86AudioRaiseVolume exec --no-startup-id pactl -- set-sink-volume 0 +5% Will be uncommented and the line: bindsym XF86AudioRaiseVolume exec --no-startup-id pactl -- set-sink vo