Note that there are some explanatory texts on larger screens.

plurals
  1. POwhat Ruby knowledge should I have?
    primarykey
    data
    text
    <p>I just discovered the <a href="https://stackoverflow.com/questions/1092376/what-c-knowledge-should-i-have">what c# knowledge should I have?</a> question and wondered about the same, but for Ruby. I consider Ruby to be my favorite programming language, and beyond learning the basics, at least what I've picked up from numerous Ruby on Rails projects and a few Ruby scripts, I've tried to learn from reading blogs like <a href="http://feeds.feedburner.com/Gluttonous" rel="nofollow noreferrer">Gluttonous</a>, <a href="http://feeds.oreilly.com/oreilly/ruby" rel="nofollow noreferrer">O'Reilly Ruby</a>, <a href="http://feeds2.feedburner.com/olabini" rel="nofollow noreferrer">Ola Bini</a>, and <a href="http://blog.zenspider.com/atom.xml" rel="nofollow noreferrer">Polishing Ruby</a>. I've also read in books like <a href="http://rads.stackoverflow.com/amzn/click/0672328844" rel="nofollow noreferrer">The Ruby Way</a>.</p> <p>However, I haven't felt fully prepared when being interviewed about my Ruby skills. I was asked once if I knew about closures and at first I responded that I didn't, but then I asked if the interviewer meant code blocks, like lambda and <code>do</code>...<code>end</code>, and he did. How did I go about 3 years of programming Ruby and trying to learn the language without learning that closures = code blocks?</p> <p>So, my question to you is what knowledge should a Ruby programmer have of the Ruby language? What would you expect, as an interviewer for a Ruby position, me to know? Just list some topics, and I'll do the reading about them. Listing Ruby-specific tools like Ruby on Rails, Rake, Rack, etc. is good too, if you think that's necessary.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload