I

have been using Ruby in personal, educational and professional settings. The journey has been great so far. I remember, right from the start, it felt like this was the language for me. It was easier to follow, no indentation problems, no weird jargons, it just felt right. It was effortless.
Keep in mind, I don't belong to the group of developers who can write assembly language code while sleeping. I am just a regular lazy software developer who likes to write lesser code yet get more returns on investments of time. I want to build more things and get them running fast.
I started with C, moved to C# (somehow I was able to fool my professors who gave me good grades in the subject), picked up Java, did some Android development, also dived into the world of python, took a nibble of Scala as well and finally got introduced to Ruby. Let's just say I was exploring my compatibility with languages. I was not very happy with my on and off relationship with python. It wanted indentation attention, I was not able to give it that. I was too young and wanted to keep exploring.

Finally, when I started with Ruby, it just clicked. And I have been in love with the language so far (Not sure if it loves me back though).

Enough of my past rant. Recently I attended Ruby Conf 2018. It was a mind-blowing experience. It humbled me. I was becoming complacent at my work but listening to the speakers made me realize how much more I have to learn. So, as recommended by one of the speakers, I picked up Ruby under a microscope book.

This post (and series of blogs coming in the future) are mainly my findings from the book, my notes, my thoughts and some googling to understand how the language I love works. I mainly make concise notes for my own memory and thought I should share with you all. If you feel my notes are BS and you can learn better from the book, you don't need to read further. I thank you for your time so far.

If you are still here, let's get started with the question:

How Ruby understands what we write?