I don’t even know where to start with talking about Geek Sublime. Vikram Chandra has long been a favorite author of mine, so I knew I was going to read this before I even knew what it was about. Then I found out that it was about computer coding and Sanskrit poetics and I was hooked.
My mom is an ex-programmer of the old school and my husband spends much of his time tinkering with code. And then the weird part, I’m a bit of an expert in Sanskrit poetics. Could this be the book that could make me understand my mom’s and husband’s obsessions with code? Who knew such a thing could exist.
Overall, I loved Geek Sublime, right down to the subtitle of the North American version: The Beauty of Code and the Code of Beauty. Chandra’s explanation of code and the history of coding was fascinating, as were the sociological differences he highlighted between coding in India and the US. Then the parallels between FORTRAN and Panini’s Sanskrit grammar – don’t even get me started.
However, I’ll admit that I was kind of bored by his long explanations of Abhinavgutpa’s theory of Sanskrit poetics. Was that because half my Master’s thesis was on this very topic? Or would others be equally numbed by the detailed explanation? If you’ve read Geek Sublime, let me know.
The one thing that I wasn’t expecting out of this book was how deeply personal it was. In addition to coding and Sanskrit, Geek Sublime gets to the heart of Chandra as a writer. I feel compelled to go back and read his debut novel Red Earth, Pouring Rain now that I’ve read Geek Sublime.
Who would like this book? I may be too close to the various topics of Geek Sublime to accurately assess who would like it, but it seems like a natural for coders with a penchant for grammar and language or a distinctly poetic streak. I’d also recommend it to lovers of comparative literature and languages. Beyond that, I’m pretty sure it is unlike most other books I’ve read.
Being the mother “old programmer”, I always saw a very strong relationship between programming and latin. I don”t know Sanskrit, but I suppose it has the same strict syntax rules as the former two. Because I started in the very early days (1964, autocoder, assembler, fortran) and people constantly asked me what is programming, I used as my analogy that it was designing the crossword puzzle, not doing the crossword puzzle. All the pieces of the puzzle must “match” to create the whole – like the syntax in latin
My son went from an undergraduate classics program into a master’s in computer science/software engineering, so there seems to be some connection! I hadn’t heard about this book before and it sounds pretty intriguing. How amazing that there were all those personal appeal factors in place for you. But maybe not so coincidental, after all, I guess!
This book sounds so interesting- I can think of a couple of people who would like it. What a happy coincidence for you that it turned out to be right up your alley! Thanks for reviewing it- I may never have noticed it, otherwise.
P.S. Love the subtitle! 🙂
I had heard of this, but didn’t really realize what it was and it sounds super interesting! I don’t really have any background on either topic, but I love the idea of an ancient language impacting the way code is written.
I don’t know anything about coding or Sanskrit poetics, but this sounds really fascinating — and I would have had no idea that that’s what this book is about based on the title.
I really have no idea if I’d like this or not. I do a lot of coding for my job and I think it’s an interesting topic, but I’m not very knowledgeable about language or poetry so I’m not sure if I’d find the long explanations enlightening or boring. I’m intrigued by the premise of the book, so I might check it out 🙂
Maybe get it out of the library. The first couple of chapters are highly enjoyable, but then it gets a little technical. I loved the early chapters on coding.
I picked this one up at Book Expo, but didn’t get around to reading it. I’m not really into coding or poetry (in the sense that they are things I really don’t know much about), but that’s one of the reasons it’s appealing to me.
Even if you don’t finish it, the first few chapters are really great. Give it a try.
Pingback: The Way Things Were by Aatish Taseer | 52 books or bust