Retaining Ruby: Start Learning Ruby Today, Even If You've Never Coded Before

by Jeffrey Crosby

Natural To Read, Easy To Write – Elegant in StyleToday's society is a fast-paced, instant gratification kind of world. Everyone wants results immediately and most have some form of technology in their homes. Computers are considered to be some of the twenty first century's most wondrous achievements. Computers are now in everything we do—they are literally everywhere from traffic light sensors to GPS locator chips that end up being implanted into animals in case that animal gets lost. Now, one can even obtain a watch that can be synchronized with one's cell phone in order to remain completely plugged into social media. But, how is this possible? What 'magic' and science allows this technology to happen? It is known that computers cannot function by themselves. A computer programmer is often responsible for typing in a sort of syntactical code to create a program. When that program is ran, the computer then translates that code into a language that the computer can understand thus allowing the computer to execute the function or functions desired by the program. What You Will Discover InsideIntroduction to RubyTaking a look at the source codeA brief history of RubyInteractive Ruby ShellLearning the SyntaxThe basics of programming ruby Would You Like To Know More? This book breaks down ruby to its roots and provides a way for even the newest programmer to learn it. The question is are you going to catch up to technology and start learning the language of the future or are you going to wake up tomorrow still stuck in the stone age?If you are ready to start learning the language of the future than scroll up and purchase Retaining Ruby.

62 pages, Kindle Edition

First published January 27, 2015

Reviews

[Letta Raven · Rating 3 out of 5]

Was good until about page 19. Could use quite a bit of editing for repetitive language and errors. for example the book says Matz invented Ruby in 1993 & it was released in 1914. Sentence structure makes things hard to read once the author begins really talking Ruby, as though unsure of the best way to describe.