Hey all,
I adore Ruby. I love everything about it. The debugging, the
community, the syntax…
But my code sorta looks like VBScript - simple and generic. I have
seen some really great Ruby code - some I can understand, others I
just can’t wrap my mind around. But how do you learn to think like that?
Can anyone recommend a book or site that teaches you to write Ruby
succinctly and rubily?
thanks,
aRi
--------------------------------------------|
If you’re not living on the edge,
then you’re just wasting space.
Hey all,
I adore Ruby. I love everything about it. The debugging, the
community, the syntax…
But my code sorta looks like VBScript - simple and generic. I have
seen some really great Ruby code - some I can understand, others I
just can’t wrap my mind around. But how do you learn to think like
that?
By reading and writing lots of Ruby code.
Can anyone recommend a book or site that teaches you to write Ruby
succinctly and rubily?
I know you have participated in Ruby Q., but have you really
explored James’ Ruby Q. web site which makes a huge amount of
interesting code available for you to read? It may be just what
you’re looking for.
Read the PickAxe book, read it for 15 to 30 minutes per day.
Force yourself to live on the command line with the ‘irb’ and ‘ri’
tools (PickAxe talks about this). Avoid a GUI for coding and use vi
or emacs (during this period a GUI will make you dumb).
And if you are into Rails about two or three months later read the
Ruby appendix in the Agile book.
Then read the PickAxe book again about 12 months later.
Participate in your local Ruby group, find yours here: http://rubyholic.com/
Start a group if one is not in your proximity.
I think “The Ruby Way” is the original poster’s best bet in terms of
writing idiomatic Ruby. It’s very much about writing Ruby that looks
like Ruby, as opposed to other languages, and that was definitely a
core part of the original question.
Another way to do it is to get the source code for a package like
Rails or Rake or RSpec or really anything nifty and useful and use
that code as a sort of combined puzzle and style guide. Figure out how
existing packages do things, and emulate them.