Skip to main content

Book Review: Raavan - Enemy of Aryavarta

It was a Sunday afternoon when I relaxed on the sofa after buying the much awaited book of the Ram Chandra Series: Raavan - Enemy of Aryavarta. Being hooked on Amish's book until I complete it for once has been my personal ritual now ever since I first read Immortals of Meluha, his first book of many. Here I am, finishing that ritual at exactly 1 am on a Tuesday morning, 36 hours after buying it.

There's something that glues me to his story-telling, something makes me forget time and I get sucked into that world completely. Somehow the language connects with my mind effortlessly.

Claiming that the number of times I've heard the story of Ramayana is a hundred wouldn't be an understatement. Perhaps it won't be an understatement for any Indian kid. But my 101th time, the story had taken a different turn. This is Amish Tripathi's Ram Chandra Series, the genre of Historic Fiction.

Although I'm a believer of the original Ramayana and most of the mythological stories, reading Amish's story about the same provides a different perception about its symbolism, the characters, and surprisingly, my own character.

Through the character of Raavan, the book tells us what a world-conquering man truly comprises of - the fire. The fire to keep going, the fire that refuses to keep him down and satisfied, the fire that takes the form of an excuse for the man to unleash his inner monster.

Raavan, even mythologically, was a person who could sing, dance, paint and be extremely passionate.
It was beautiful to perceive love through an artist's heart, the depth to which he loved a woman, and the rage which filled him when he lost it.

Surprisingly though, I could see through the author being influenced by the current world's events to write down certain things such as a conversation about women not being allowed inside certain temples, which might be coming from the huge Sabarimala controversy some months ago. The names of certain new characters also seemed to be inspired from other movie and show characters.
It's obviously natural for authors to be influenced by world events in their writing but the fact that I could actually recognize the influence was new!

Anyway, I cannot think of much without giving away the story, and although it's not very unprecedented, it is definitely engaging!

Jai Shri Rudra!


Post a Comment

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

An introduction to APIs

API is an acronym for Application Programming Interface. Let's start with first defining some basic terms: Browser: These are browsers. To visit any website on the internet, you need a browser. Server: Hmm, this is tough. In simple words, server is a computer. Yes, just like the laptop, or PC at your home. The only difference is that it does not have a screen. Of course, there are other differences in technical specifications, but at its core, the server is just, simply, a computer. That's it. So why is it called a server? Because it serves . When you go to a website like , your computer connects to the internet and gets you your search result. But your computer's internet connection has to get that result from somewhere, right? If the google search result is giving you some answers, the answers have to come from somewhere. What is that place? The answer to that some place is: a server. When you click on the search button on google, or hit enter after typing, &q

Review: Nestjs - Finally a scalable way to build APIs

I have been thinking about this for a long time. There HAS to be a defined way to build APIs in a scalable way.  If you have used Node, Express, etc in your side projects, you might have felt that after a point in development, debugging truly becomes a pain. Sure, enterprise-level API codes are great. But a lot of times, these configurations are too much, and probably not even needed in other projects. To be honest, I haven't seen a lot of Open-Source API codes either to make a judgement on how experienced developers build their APIs. Anyway, I came across an amazing framework recently, and I think if you are coding a complex API, this should be your way to go. Nest.js Nest.js is a framework for building efficient, reliable and scalable server-side applications.  You essentially break your APIs into controllers, services, and modules, which allow you to modularize the smallest of functionalities in your endpoints or the API as a whole. Why is modularizing important? As I have talk