Ruby on Rails Tutorial Michael Hartl

Review to one of the most popular Ruby on Rails tutorial
22 June 2017   5717
Ruby

A dynamic, open source programming language with a focus on simplicity and productivity.
 

Ruby on Rails

Ruby on Rails (RoR) - a framework written in the Ruby programming language.

When you will start to learn RoR, one of the first book that will be recommended to you is a Ruby on Rails Tutorial by Michael Hartl. This is one of the most popular newbie’s Ruby guide. At the moment, it has 6 editions and translated to many languages. It consists of 14 chapters and 744 pages. Thru these pages, Michael will teach you how to develop custom web applications, using the popular Ruby on Rails framework. It will also focus on the general principles of web development.

Ruby on Rails Tutorial by Michael Hartl
Ruby on Rails Tutorial by Michael Hartl

Author

Michael Hartl is former Y Combinator alumni, he has a Ph.D. degree in theoretical physics and he was teaching at Caltech. His book guides you through building a Twitter clone in Rails. This is the only Rails book that does test-driven development the whole time. This approach is highly recommended by the experts.

Michael Hartl
Michael Hartl

By including Git, GitHub, and Heroku in the demo examples, the author really gives you a feel for what it’s like to do a real-life project. The tutorial code examples are not isolated.

Book targeting

The book is targeted to a Rails newcomer, not a pro web developer, but general programming skills are needed. Author assume that you are a beginner, so, he will introduce whole Rails ecosystem to you. So, some time will be spent to install version control system called Git and text editors for coding.

What's inside

Inside Ruby on Rails Tutorial
Inside Ruby on Rails Tutorial

Building a Twitter clone by this book will be in a “hard way”, without a gem for user authentication. So, you will be involved in building different models (user, micropost and session), creating partials, passing information between different classes and handling errors.

A micro-blogging app is used to slowly, step-by-step walk through the different Rails features. The tutorial also explains some of the “magic” that goes on under the covers that Rails provides for you.  

Whole book is like a perfectly written program, modular, without any bugs or “empty code”. Author specify the exact versions of every gem, Rails and databases that are used. The book has zero errors, so, every time you will have a bug, it is an issue on your end.

True coder's habits

Usage of GitHub, Heroku, branching makes you feel like you are working on a real-life project, being a “real coder”. Number of gems, used in a test project is not very big, only the most common were used. Most of the things are made by hands.

Book is focused on testing. It starts from RSpec unit tests, then integration tests. TDD approach is followed for a long time where the tests come before the code, a practice that is commonly used by the coders. It will help you to create a good coder habits like running tests before and after merging a branch and refactor your code to reduce duplicates and increase application’s stability.  

Here is a good quote from the book:

If you ask five Rails developers how to test any given piece of code, you’ll get about fifteen different answers—but they’ll all agree that you should definitely be writing tests.
 

Michael Hartl
Ruby on Rails Tutorial

Also, Tutorial teaches you how to use Terminal properly. You will learn how to set up a sublime text shortcut, how to navigate file structures, create files and other shortcuts that will help you. Terminal will be your program associated with programming and technical expertise.

Conclusion

Ruby on Rails tutorial is a long course and it needs assiduity and diligence. But you can learn a lot from it.

It covers everything someone new to developing Ruby on Rails applications could need. It’s a good fit for people new to web development and new to Rails.

Ready to master Rails? Get this book. 

Charles Nutter. How to move your Ruby project to JRuby and why

Charles Nutter works on JRuby and JVM language support at Red Hat.
03 October 2018   1171

— How did you get into programming and into Ruby world?

— In 2004, I was working at a government contracting firm as a Java Enterprise Architect. I was in charge of a large mainframe conversion for the United States Department of Agriculture, which meant I spent a couple weeks a month in the Washington D.C. area. One of those trips coincided with RubyConf 2004, and since a close friend had been recommending I look at Ruby, I decided to attend. So there I was sitting in a Ruby conference without ever having learned Ruby...and I understood every piece of code, every example. I was amazed and vowed to find a way to bring Ruby into my Java world.

— Which projects are you working on now?

— My primary role is as co-lead of JRuby. This also means supporting several side projects like our native-library backend (Ruby's FFI library is maintained by us using this backend on JRuby) and our String encoding subsystem (an elaborate port of the logic from CRuby). I also do much of the outreach to the community and try to make sure our users are getting their issues addressed. There's always plenty to work on!

— Which one would have the biggest general impact from you opinion?

— I like to think that JRuby, while not the most popular JVM language, has at least helped to change the JVM platform. Because of our collaborations with Sun Microsystems, Oracle, and others, we have solid dynamic language support at the JVM level along with many other projects to support alternative languages. The JVM today is a much more hospitable home for non-Java languages than it used to be, and I hope we've played some small part in that change.

— Which languages are you writing on in your everyday life? Which one do you like most? Why?

— Most days I write in a mix of Ruby and Java, since JRuby is implemented using both. I like both languages for different tasks. Ruby is a better language for building applications that need to evolve and adapt quickly. Java is a great language for writing high-speed, reliable libraries and services. JRuby gives you the best of both worlds!

— Do you like to program in Java?

— I do, especially with all the language improvements that have been added recently, like lambdas (closures or blocks in Ruby) and the new "var" syntax for declaring local variables when the static type is unambiguous.

— What do you think about Rust?

— Rust is a great language! I did a lot of C++ development in my college years, and I can tell you right now if I'd had Rust available then I would have used it. I'm especially jealous of the static-typed ownership model, which helps avoid thread-safety issues like races and data corruption. I hope to see other languages adopt this pattern in the future.

— What do you think about the Ruby language perspective? Is it or its community dying?

— After all these years working on JRuby, I do still love Ruby syntax and the Ruby way of doing things. However I worry that the language is held back too much by limitations of its primary runtime. JRuby has been fighting to make true parallel threading a reality for Ruby developers, but still today the vast majority of Ruby services are run using multiple isolated processes, wasting tremendous amounts of CPU and memory resources. I believe this is due to the C API for writing Ruby extensions being so large and so invasive...it prevents many improvements -- including parallel threading -- from being developed. Hopefully we'll see this change some day.

— Which upcoming or not well-known features of Ruby language would rush in future?

— I look forward to strings becoming immutable-by-default, as they are in most other languages. Parallel programming would be much simpler if more of Ruby's objects supported pure-immutable or "deep freeze" semantics. It's a bit like the Rust ownership model...if you're going to be sharing an object across threads, choose the version of that object that you know can't be modified anymore. This extends to arrays, hashes, and just about every other mutable object in Ruby: we need to make it easier to lock down mutable data.

— Could you give me an advice on how to move my ancient monolithic project to JRuby? And should I?

— The first question really is whether such a move would benefit you. There's many good reasons to consider a move to JRuby:

  • Reducing CPU  and memory costs in a shared hosting environment by utilizing JRuby's true parallel threading
  • Deploying a Ruby application into a JVM-heavy environment, such as used by larger financial or government organizations
  • Needing access to libraries that only exist on the JVM, or that are more portable or scalable on the JVM than their Ruby or C equivalents
  • Getting a little performance boost out of CPU-heavy or concurrency-heavy applications.

— I would say if your application is scaling well and not costing you too much today, perhaps you don't need to make a move. But if you decide you need more out of Ruby, here's the process for migrating:

  • Do a clean bundle of your application, paying special attention to C extensions you may be using. You can also do this bundling *on* JRuby, and then deal with missing or unsupported libraries one by one.
  • For each extension, search for a JRuby equivalent. We have some pages on the JRuby wiki to help with this. Most popular libraries have JRuby versions. If no JRuby version exists, you may look for a pure-Ruby version (it might be fast enough on JRuby) or a JVM library (in Java or Scala or Clojure or whatever) that could be used as a replacement.
  • Once your bundle completes, you should have a working JRuby application! We've worked very hard on compatibility, and try to be responsive if users find new issues, but a successfully-bundled application is expected to work.

The steps beyond this involve deciding how to take advantage of your newfound power: how many threads to throw at a given server, what you're going to do with all the money you're saving, etc.

— What should nowadays students learn to become good programmers?

— When I was at university, my earliest computer science courses used the Scheme language, a Lisp-like functional language that's great for teaching the fundamentals of programming. I still recommend that serious new programmers work through at least some of the Structure and Interpretation of Computer Programs book from MIT. Beyond that, I'd say learn as many different and unusual languages as you can; they'll all give you new ideas and new ways to look at programming problems.

— How do you keep yourself motivated for programming? Have you ever been "burned-out"?

— Burn-out is a real problem in our industry, and working in open source brings with it huge amount of stress. We've all felt that way sometimes...too much work to do and not enough time to do it, missing out on time with family and friends, ignoring our own health so we can fix one more bug. These days I try to center myself by keeping up with hobbies: playing video and board games, learning to play guitar, studying foreign languages, and traveling around the world to meet new friends. There's always this nagging workaholic telling me to get back on the job, but I'm learning how to maintain the right balance.

— What do you think about Russia and what do you expect of the upcoming RubyRussia event?

— I love Russia, and my speaking trips the past few years have been some of the most rewarding of my life. This will be my fourth visit, having been to Saint-Petersburg, Moscow, and Novosibirsk (!!!) previously. I'm looking forward to returning to Moscow and meeting the RubyRussia community I've heard so much about!

Questions by Dmitry Matveyev PM at Evrone https://www.facebook.com/matveyev.d