You’ve got the building blocks of Ruby out of the way, great! Now it’s time to get into the fun stuff… how do we combine those building blocks in the most efficient and elegant ways to produce the programs we’d like to write?
The concepts you’ll learn here are often less specific to Ruby itself and more widely applicable to any object-oriented language. That’s because the fundamental concepts are just that… fundamental. Don’t repeat yourself. Modularize your code. Have your classes and methods only do one thing. Show as little of your interfaces to the world as you can. Don’t make methods or classes heavily dependent on each other. Be lazy. These will take some time and practice to implement effectively, but you’ll already be taking a big step towards creating high quality code just by finishing up this section.
There’s a lot to do here but stick with it! We’ll start with the Codecademy lessons, which are interspersed with their projects so you’ll get a chance to apply what you’re learning. The Beginning Ruby book will help you understand the material a bit deeper, which will be important when you are creating your own projects next.
Look through these now and then use them to test yourself after doing the assignment:
Classes and Methods:
- What is an implicit return?
- What is a class?
- When should you use a class?
- How do you create a class in your script file?
- What is an instance of a class?
- What is the difference between the CamelCase and snake_case styles of naming?
- How do you instantiate a class?
- How do you set the state of your new instance?
- What should be done in the
- What is a class method?
- How is a class method different from an instance method?
- How are methods you already know like
#sort etc instance methods?
- What’s the difference between how you declare a class method vs an instance method?
- What’s the difference between how you call a class method vs an instance method?
- What is an instance variable?
- What’s the difference between an instance variable and a ‘regular’ variable?
- What are “getter” and “setter” methods used for?
- What is the difference between a “getter” and a “setter” method?
- How do you make instance variables readable outside your class? Writeable? Both at the same time?
- Can a class call its own class methods?
- What’s the difference between when you would use a class variable and when you would use a constant?
- What’s the difference between a class and a module?
- When would you use a class but not a module?
- How does inheritance work?
- Why is inheritance really useful?
- How do you extend a class? What does that mean?
- What does
#super do? Why use it?
- What is scope?
- When can you start using a variable?
- When is a new scope defined?
- When are methods in scope?
- What is a private method?
- What is a protected method?
- How are private and protected methods different?
- What does “encapsulation” mean?
- Do Codecademy Ruby sections 9 and 10:
1. Object-Oriented Programming, Part I
2. Project: Virtual Computer
3. Object-Oriented Programming, Part II
4. Project: Banking on Ruby
- Take a brief break from code and learn more about the world of Ruby:
1. Read about the History of Ruby
2. Read about Open Source Culture in Section 1
3. Read about where you can find Ruby’s Community
- Read Beginning Ruby Chapter 6:
Classes, Objects, and Modules. It will extend your knowledge deeper than Codecademy alone.
- Read Beginning Ruby Chapter 7:
Projects and Libraries
- Read Beginning Ruby Chapter 8:
Documentation and Error Handling but skip the stuff on Testing (pgs 175-179)
- Read through these reinforcing posts by Erik Trautman to help you answer the questions in the “Learning Outcomes” section:
1. Ruby Explained: Classes
2. Ruby Explained: Inheritance and Scope
- Read the Bastard’s Chapter on Error Handling to reinforce your understanding of dealing with errors.
- Glance over the Ruby Style Guide so you have an idea of how to make your code look more professional.
- Make sure you can do Quiz #5 from Code Quizzes.
- Make sure you can do Quiz #7 as well.
- Make sure you go back up and look at all the questions from the “Points to Ponder” section. See if you can do most of them without looking back through the text.
This section contains helpful links to other content. It isn’t required, so consider it supplemental for if you need to dive deeper into something.