If I had taken the time to install it straight away I would have saved a lot of wasted effort.
Here's my 'rvm tutorial in a HN comment':
To install rvm, run this:
$ bash < <( curl http://rvm.beginrescueend.com/releases/rvm-install-head )
[[ -s "$HOME/.rvm/scripts/rvm" ]] && . "$HOME/.rvm/scripts/rvm"
To install any Ruby, 'rvm install 1.9.2', for example. To switch Rubies, 'rvm 1.9.2'.
That's it! Pretty easy. I like to take two further steps, though: create a gemset per application, and set up .rvmrc files to switch to the right ruby automatically.
To do the gemset thing, 'rvm gemset create gemset_name'. You can switch to a specific gemset at the time you switch rubies with 'rvm 1.9.2@gemset_name', or after with 'rvm gemset use gemset_name'
Once you've got that going, make a '.rvmrc' file in the root of your project, and put in it the rvm command to switch to your ruby/gemset. "echo 'rvm 1.9.2@gemset_name' > .rvmrc" is probably the easiest way to do this. Then, when you switch to your project, you're in the correct ruby and gemset automatically. When you have 9 or 10 projects on 4 different Rubies, this helps a lot...
Then what should have been ten minutes turns into three hours and I burn up all the time I could have been building something. Granted I usually learn something along the way, but it would be awesome if people provided some more details as part of their tutorials.