#126 in Computers & technology books
Use arrows to jump to the previous/next product

Reddit mentions of Eloquent Ruby (Addison-Wesley Professional Ruby Series)

Sentiment score: 16
Reddit mentions: 26

We found 26 Reddit mentions of Eloquent Ruby (Addison-Wesley Professional Ruby Series). Here are the top ones.

Eloquent Ruby (Addison-Wesley Professional Ruby Series)
Buying options
View on Amazon.com
or
    Features:
  • Dayan Zhanchi Three Layer 3x3x3 Speed Cube
  • Designed for speed solving
  • One of the best speed cube in the world
Specs:
Height9.13 Inches
Length7 Inches
Number of items1
Release dateFebruary 2011
Weight1.51678036256 Pounds
Width0.95 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 26 comments on Eloquent Ruby (Addison-Wesley Professional Ruby Series):

u/samort7 · 257 pointsr/learnprogramming

Here's my list of the classics:

General Computing

u/postmodern · 27 pointsr/ruby

Sidebar

  • Link to /r/rails and /r/ruby_proposals. Encourage all Rails-centric posts/questions to go in /r/rails.
  • Remove some of the Rails-centric books from the sidebar, add more Ruby-centric books (such as The Well Grounded Rubyist and Eloquent Ruby).
  • Link to TryRuby.
  • Link to the GitHub (Free) Sign-Up page.
  • Link to the RubyGems Sign-Up page.
  • Link to RVM.

    Moderation

    Remove link/blog-spam. It's kind of pointless to read a summary on RubyInside, when I can read the original full-article written by the primary-author/project-lead on their own blog. Summaries of complex issues which span multiple blog-posts are OK though, I enjoy reading those.

    Also, please no more articles about simple things like recursion or Arrays (that's what TryRuby and RubyKoans are for).

    What's this about a Contest? Sounds fun.
u/sprayAtMeBro · 15 pointsr/ruby

A friend recently passed on his copy of Eloquent Ruby. It's slightly outdated but still holds up.

u/LegionSB · 15 pointsr/ruby

> Where can I learn the ruby way of things? for ex: I think ruby does str.reverse! rather than str = str.reverse()

You want Eloquent Ruby. It's a book about writing idiomatic Ruby, which is what you're asking about.

The Pickaxe book and POODR are both excellent books that you also want, but Eloquent Ruby is probably the best book for what you're specifically asking about.

u/colonpee · 14 pointsr/ruby

You want Eloquent Ruby! This book is perfect for someone that is coming from a different language and has some of the basics of Ruby down already.

u/OtavioHenrique · 9 pointsr/rails

I advise you to learn ruby first, it will be good for your understanding, rails is a huge framework that helps the developer a lot, but on my opinion, know Ruby is a key for pretty understanding Rails.

I usually recommend eloquent ruby: https://www.amazon.com/Eloquent-Ruby-Addison-Wesley-Professional/dp/0321584104

But the are a lot of good books.

Some free content:

https://launchschool.com/books

https://www.ossblog.org/study-ruby-programming-with-open-source-books/

Some Udemy courses are good too.

u/jb3689 · 6 pointsr/ruby

All of the OO stuff is great but I've found it to be mostly subjective and repeating a lot of the same old boring stuff. I've always felt that programming with heuristics works better for me (e.g. least-visibility principle, sprinkling design patterns where it makes sense, focusing on interfaces, doing mostly TDD but trying to test meaningful contracts instead of being hardcore about red-green-refactor, etc)

Russ Olsen's Eloquent Ruby is still, and will probably always be, my favorite. It taught me how to right Ruby "the right way" by teaching me to learn the core libraries in-depth and explaining what the conventions were in them

Outside of that, Jesse Storimer's books are all good for learning how to use OS features from Ruby which is something I find critically lacking instruction of in the Ruby community

u/KryptykPhysh · 6 pointsr/ruby

Eloquent Ruby was one that really helped me out.

u/farmerje · 5 pointsr/learnprogramming

I recommend Practical Object-Oriented Design in Ruby (aka POODR) and Eloquent Ruby.

I'm expert at C, Ruby, and Python, so if you post code examples of Ruby code you feel isn't idiomatic to gist.github.com I'm happy to take a look and offer feedback. I co-founded Dev Bootcamp, so I'm also familiar with the bumps along the way folks have when learning Ruby, even (and sometimes especially) if they're coming from another language.

The main thing to understand about Ruby is that everything is an object. To wit,

Foo = Class.new
foo = Foo.new
puts foo.object_id

Particular classes are instances of the class "Class," if you can wrap your head around that. Objects talk to each other by passing messages around, i.e., methods. In fact, you can define methods on individual objects (although nobody ever does this):

name = "Jesse"
def name.bark!
puts "woof woof"
end
name.bark!

But this is what's happening when you see code like

class Foo
def self.bark!
puts "woof woof"
end
end

The "self.bark!" sometimes seems like arbitrary syntax used to define class methods (or static methods as they're called in some OOP languages), especially to people coming from Java where you have these seemingly-magical keyword preludes. In Ruby you just define methods on objects, period. Classes are objects, too, and "def self.whatever" is the same as "def Foo.whatever". There's a nice nod to referential transparency there that you don't see in many OOP languages.

Every method is defined on some object, even "global" methods. Exercise: when you define a global method in Ruby what object does it get defined on?

When you need higher-order functions Ruby uses blocks, which are more like functions in JavaScript than lambdas in Python (e.g., they can contain arbitrary code, not just a single expression).

If you understand those three things -- everything is an object, objects communicate via messages called "methods", higher-order functions can be defined using blocks -- you understand about 95% of how Ruby thinks about the world.

I'll add, just because you're a C guy, Ruby "pretends" it doesn't really have a class/object distinction, but the default Ruby interpreter (MRI or sometimes CRuby) does actually have separate structs for classes and objects. It's really a language-level thing.

u/chrisledet · 5 pointsr/rails

This and Eloquent Ruby. Best Ruby books.

u/abashinyan · 5 pointsr/ruby

Practical Object-Oriented Design in Ruby: An Agile Primer (Addison-Wesley Professional Ruby Series)

www.amazon.com/Practical-Object-Oriented-Design-Ruby-Addison-Wesley/dp/0321721330/ref=sr_1_6?ie=UTF8&qid=1398842637&sr=8-6&keywords=ruby#reader_0321721330

Eloquent Ruby

http://www.amazon.com/Eloquent-Ruby-Addison-Wesley-Professional-Series/dp/0321584104/ref=sr_1_9?ie=UTF8&qid=1398842637&sr=8-9&keywords=ruby

Metaprogramming Ruby: Program Like the Ruby Pros

http://www.amazon.com/Metaprogramming-Ruby-Program-Like-Pros/dp/1934356476/ref=pd_rhf_se_s_cp_6_BXWQ?ie=UTF8&refRID=02JTWKY2ZDHPVZWX181R

u/optimal_persona · 3 pointsr/ruby

I'm getting good mileage out of David Copeland's Build Awesome Command-Line Applications in Ruby 2 (2013). For Ruby-specific best practices (I'm coming from PHP), Sandi Metz' Practical Object-Oriented Design (2019) and Russ Olsen's Eloquent Ruby (2011) are opening my eyes to how it's done here. In particular, Metz' focus on the role of messages in OO design has changed my approach to planning and testing - just in time for a critical project.

u/CaptainKabob · 3 pointsr/ruby

I would really recommend reading Eloquent Ruby. It's a good structured introduction to practical Ruby.

u/Slackwise · 2 pointsr/programming

If you want more guidelines and a further understanding of Ruby idioms, take a look at Eloquent Ruby.

u/pornlord · 2 pointsr/learnprogramming

Depends what you want to do in long run. If you are interested in System administration or networking, learn Perl.

If you just want a job and learn a cool scripting language, go for Python. Since you have done Python, it should not be hard for you to pick up. Start with this, that would be my advice.

If you are looking for web development, go for Ruby. Ruby is a bit more object oriented than Python or rather too high level abstraction. So to appreciate Ruby code and exploit its abstraction and not get overwhelmed, it would do good, if you did Python at first. It will make learning or appreciating Ruby easier. It will be a good foundation to learning Rails, a web framework. Do, Ruby if you are interested in web development and so holds for Python. Anyways Ruby is fun to learn. If you are comfortable with Java and just want a quick start, I recommend eloquent ruby.

You may have programmed in C++ but going back from Java, you may feel awkward. I will put the C++ as the last language in the list of priority of learning.

So in order of prioritising what you want to learn, my list would be

  • Python
  • Perl / Ruby depending on whether you like networking or web applications.
  • C++

    On a side note, if you are going for software engineering. It does no harm to learn another paradigm. You are only familiar with object oriented and procedural paradigm. If you are interested in broadening your SE skills try to sharpen up on functional programming. Haskell or Clojure (JVM implementation of Lisp and somewhat favoured by web developers) are good starting points.
u/aparadja · 2 pointsr/ruby

Eloquent Ruby is one of the best programming books I've ever read. I highly recommend it. It'll get you started quickly with the basics, and then make you fall in love by showing the simple and powerful beauty of the language's design.

The poignant guide (the cartoon fox thing) is funny and smart, but Eloquent Ruby will make you really grok Ruby.

u/DudeManFoo · 2 pointsr/ruby

Most of us started this way... if not with Ruby then another language...

Then you get more experience and start writing better code... some of the shortcuts take a while to get...

This book has quite the collection and is pretty much how most of us do it...

EDIT : OOPS... wrong book... that is a great one, but I meant this one for your level

u/[deleted] · 2 pointsr/ruby

sorry to hear you're having trouble; i get my ass kicked all the time.

if programming languages were like poems, i'd liken things like C# to an epic and ruby to a haiku. both are packed full of meaning, but the approach toward expressing it is radically different (imho: just an impression, keep the hatches battened down). the ruby community focuses very much on readability, in the sense that code sometimes reads more like pseudocode, or even just regular text, than i've seen in other lanaguages. this focus on readability is tightly coupled with a preference for terseness wherever and however possible: things like dry (don't repeat yourself), etc. are heavily emphasized.

sometimes it feels to me like i'm meeting a new person when i learn a new language, tool, etc.: it can go well or poorly, but regardless it takes a while to learn each other well enough in order to communicate effectively. the only way to expedite the process is familiarity. if familiarity is in short supply, patience appears to be the only way forward. disagreements will arise, but i try to look at those as opportunities to potentially broaden my perspective.

i'd recommend just taking some time in a low-pressure environment to work through some examples (small, easy ones just to get the feel for it) and read things like the pickaxe or the ruby way. eloquent ruby is on my reading list as well.

as far as editors go, i tried aptana (eclipse), rubymine, etc. i finally settled back on vim, with a few plugins to help along. so far, i've got pretty much everything i need out of an ide - granted, i do tend to use nix as an IDE. if you'd like some more information on that, here's a blog post i wrote a while back about my setup then. it's for ubuntu, but some of the gems, etc. it references may be helpful. of particular note is rubocop, which is a linter for ruby. about the only things i don't have via vim (either as part of default vim or via plugin) is code-completion (honestly don't use it that much) and a built-in debugger (again, nix as an IDE, plain old ruby debug gets me by. yes, pry. i know.). for built-in debugging, there's vim-ruby-debugger, and for autocompletion there's youcompleteme. i haven't personally used those plugins yet, but they're on my list to try out. there are probably others as well.

hope this helps.

u/vaxinate · 2 pointsr/ruby

this is kind of a silly book, but it's about ruby. and pretty entertaining honestly. Why's Poingniant Guide to Ruby

EDIT: i hadn't read this in a long time so i was skimming it, but seriously if you can get past how out there the book is, its honestly a pretty legit way to learn ruby.

EDIT AGAIN SHIT: also Eloquent Ruby

u/kanjibandit · 2 pointsr/rails

How well do you know Java? I suspect you may be overestimating the time to it will take you to get comfortable in Ruby. Learning your first language is always harder than the second, because you're really learning two separate things: 1) how to program, and 2) the language syntax. The second time around, it's largely just a new syntax. Most of your knowledge of how to code will transfer. True, Ruby will introduce you to new concepts, but I think you'll find them rather more like new superpowers than like new obstacles.

Specific recommendations:

For Ruby, I like the book Eloquent Ruby

For Rails, I like Michael Hartl's Rails Tutorial

For fun and practice, look at Ruby Koans

u/hc5duke · 1 pointr/ruby

+1 for Ruby Koans.

I also recommend Eloquent Ruby to anyone starting out in Ruby and/or Rails.

u/michellemustudy · 1 pointr/ruby

I’ve heard great things about The Odin Project.

Aside from Sandi Metz book, I personally learned a lot from Russ Olsen’s book Eloquent Ruby.

u/chris-herring · 1 pointr/learnprogramming

There are great Ruby books that aren't aimed squarely at newbies. Just a couple are:

Practical Object-Oriented Design in Ruby is excellent.

Eloquent Ruby is great as well.