FAQ: The Zen of Ruby - Call and Response


This community-built FAQ covers the “Call and Response” exercise from the lesson “The Zen of Ruby”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn Ruby

FAQs on the exercise Call and Response

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!


After some confusion and googling i found this very usefull explenation on stackoverflow, i thought its maybe valuable for others too:
Normally type checking is not done in Ruby, but instead objects are assessed based on their ability to respond to particular methods, commonly called “Duck typing”. In other words, if it responds to the methods you want, there’s no reason to be particular about the type.

direct link to source: https://stackoverflow.com/questions/15769739/determining-type-of-an-object-in-ruby#15769829