Roughing Through Rudimentary Ruby
When most people hear the word “Ruby”, their first thoughts automatically jump towards “expensive”, “luxurious”, and“Mohs scale of hardness”. However, and somewhat unfortunately, this post will not be delving into traditionally ruby mining. Instead, it will focus on my journey through Ruby (please note the proper case). Ruby is a computer programming language that entered the world in the mid 90s and has gained a substantial following over the years. It was created in Japan and heavily influenced by Pearl, Ada, Lisp, and a variety of other languages. The program itself was created with programmer happiness in mind. What does that mean? Well, I’m still figuring that out; I’m sure that it includes a vast array of different benefits exalted by the Ruby community. Currently, in my pleb mind, it boils down into the following three things:
- It reads somewhat like English. win….now I just have to learn how to read “somewhat like English”.
- RubyGems. A digital library of thousands of pre-written code. win.
- TDD (test driven development). Basically, it is easier for programmer’s to run their own tests to make sure their code works. proofreading good.
As you can probably tell from my post, I am a complete novice in Ruby-land. If you want a novice’s perspective on Ruby, keep reading. This week I was assigned to read a FREE (yes, I am cheap) e-resource Why’s Poignant Guide to Ruby. Think of it as one of the Dummies books+awkwardly drawn cartoons+ an overly exuberant and slightly spastic author. For me, none of those are really negatives, especially when associated with “FREE”, but I digress. The book provides an understandable explanation of basic concepts such as methods, classes, and variables. If you are interested in learning about Ruby, becoming familiar with the jargon, or maybe solidifying introductory concepts, definitely take a gander at the book. However, if you are looking for a book that tells you exactly how to create your own app, this resource may not be your first choice. Personally, this book helped me conceptualize the inner-workings of Ruby a little bit better; it made the pieces fit together a little better.