[Why's] 4.Floating Little Leaves of Code

• http://mislav.uniqpath.com/poignant-guide/book/chapter-4.html
• 1. The Leaf as a Status Symbol in Ambrose
• Animal Perfect L.L.C. is a firm, which build new animals and salvage old-style animals for parts.
• Starmonkeys are one of such animals.
• "A lot of Rubyists like to think of methods as a message."
• A Ruby program consists of two parts:
  
  1. Defining things.
  2. Putting those things into action.
• Assignment (=) is the simplest example of defining something in Ruby.
• Starmonkey creation process looks in Ruby as follows:
  

  starmonkey = ratchet.attach( captive_monkey, pipe.catch_a_star ) + deco_hand_frog
  

• 2. Small and Nearly Worthless
• Nil: "In Ruby, nil represents an emptiness."
• False: "Generally speaking, everything in Ruby has a positive charge to it. This spark flows through strings, numbers, regexps, all of it. Only two keywords wear a shady cloak: nil and false draggin’ us down."
• True: "To be honest, I can’t be around someone who always has to be right. This true is always saying, 'A-OK.'"
• 3. Chaining Delusions Together
• TBW
• 4. The Miracle of Blocks
• TBW

[Why's] 3.A Quick (and Hopefully Painless) Ride Through Ruby (with Cartoon Foxes)

• http://mislav.uniqpath.com/poignant-guide/book/chapter-3.html
• "My conscience won’t let me call Ruby a computer language." A fascinating expression.
  
• "We can no longer truthfully call it a computer language. It is coderspeak. It is the language of our thoughts." Okay. I agree with the author about this characteristic of Ruby but...
  
  • Schemers may say "We use not English but abstract trees of data and codes when we design and analyze programs.",
  • Haskeler may say "You can't prove your correctness. We should change our way of thinking. Category theory is an alternative mathematical...",
  • Common Lisper may say "Ah, that's a kind of the loop macro. Some love that kinda stuff. But others don't. Enjoy."
• "Try to focus on the look of each of these parts of speech. The rest of the book will detail the specifics. I give short descriptions for each part of speech, but you don’t have to understand the explanation. By the end of this chapter, you should be able to recognize every part of a Ruby program." This is practical and effective way to start introducing a language. This long section, "2. The Parts of Speech" provides exactly this type of quick tour of Ruby. Good.

[Why's] 2. Kon’nichi wa, Ruby

• http://mislav.uniqpath.com/poignant-guide/book/chapter-2.html
• This chapter looks a scene setting or an concensus process between the author and readers. The chapter contains little information about Ruby itself.
• In a nutshell, important information in the chapter as an introductory book for Ruby is:
1. At first sight, the author thought Ruby was meaningless. But later they clicked. (That can happen to you as well.)
2. By learning Ruby, you may be able to improve your brain performance.
3. Using Ruby costs nothing.
4. Enjoy cartoons with foxes.

[Why's] 1.About this Book

• http://mislav.uniqpath.com/poignant-guide/book/chapter-1.html
• Haha. Just nonsense.

Why's (Poignant) Guide to Ruby

Let me get something straight: I just would like to learn writing programs in Ruby. I don't need any grammatical explanations if I can write Ruby programs without them. Moreover, I don't need any author's grammatically-looking half-baked explanations, because they are just confusing. Basically, usage and pragmatics are important for me.

The next material I would like to try is http://mislav.uniqpath.com/poignant-guide/book/. Hope this meets my requirements.