Implementing Inheritance Wisely in Ruby | CodeSignal Learn

Implementing Inheritance Wisely in Ruby | CodeSignal Learn

Introduction

Welcome to another lesson of the Clean Code in Ruby course! In previous lessons, we've explored foundational concepts like the Single Responsibility Principle, encapsulation, and constructors, which are essential for writing clear, maintainable, and efficient Ruby code. In this lesson, we'll focus on wisely implementing inheritance in Ruby. By understanding the role of inheritance, we will learn how to apply it effectively, enhancing code readability and organization while maintaining the principles of clean code.

How Inheritance is Important to Writing Clean Code

Inheritance is a cornerstone of object-oriented programming that allows for code reuse and logical organization. It enables developers to create new classes based on existing ones, inheriting their methods and properties. When used appropriately, inheritance can lead to more streamlined and easier-to-understand code. Code Reuse and Reduction of Redundancies : By creating subclasses that inherit from a base class, you can avoid code duplication, making your application easier to maintain and extend. Improved Readability : Logical inheritance hierarchies can improve the clarity of your Ruby code. For example, if you have a base class Vehicle, with subclasses Car and Motorcycle, the organization makes intuitive sense and clarifies each class's role. Alignment with Previous Concepts : Inheritance should respect the Single Responsibility Principle and encapsulation. Each class should have a clear purpose and should keep its data protected, whether it's a base class or a subclass.

Best Practices When Using Inheritance

To effectively leverage inheritance in Ruby, it's important to follow several best practices: Favor Composition Over Inheritance : In some cases, inheritance might lead to tightly coupled code, which isn't ideal. In such cases, using composition through Ruby's modules and mixins might be a better option. Clear and Stable Base Class Interfaces : Ensure that base classes provide a consistent and limited interface to prevent subclasses from overly depending on implementation details. Avoid Deep Inheritance Hierarchies : Deep hierarchies can complicate understanding and maintaining code, leading to harder debugging and modification processes. Common pitfalls include overusing inheritance to model relationships that might not naturally fit an "is-a" relationship and using inheritance for code sharing without considering logical organization.

Sign up

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal

Bad Example

Let’s explore a bad example to understand the misuse of inheritance in Ruby: class Person attr_accessor :name, :age def work puts "Person working" end end class Employee < Person attr_accessor :employee_id def file_taxes puts "Employee filing taxes" end end class Manager < Employee def hold_meeting puts "Manager holding a meeting" end end In this example: The hierarchy is too deep, with Manager extending Employee, which extends Person . Person having a work method might be inappropriate because not every person works, making the base class less general. The inheritance might be forced where a Manager "is-a" Person, but the middle class Employee may not be necessary as a separate entity.

Refactored Example

Now let's refactor the previous example to follow best practices: class Person attr_accessor :name, :age def initialize(name, age) @name = name @age = age end end class Employee attr_accessor :person_details, :employee_id def initialize(person_details, employee_id) @person_details = person_details @employee_id = employee_id end def file_taxes puts "#{person_details.name} filing taxes" end end class Manager < Employee def hold_meeting puts "#{person_details.name} holding a meeting" end end In the refactored example: Person no longer has a work method, making it more general. Employee now uses composition to include a Person object instead of inheriting from it. This simplifies the hierarchy. Manager still inherits from Employee, maintaining a logical structure but with reduced complexity.

Ruby

class Person
  attr_accessor :name, :age

  def work
    puts "Person working"
  end
end

class Employee < Person
  attr_accessor :employee_id

  def file_taxes
    puts "Employee filing taxes"
  end
end

class Manager < Employee
  def hold_meeting
    puts "Manager holding a meeting"
  end
end

Ruby

class Person
  attr_accessor :name, :age

  def initialize(name, age)
    @name = name
    @age = age
  end
end

class Employee
  attr_accessor :person_details, :employee_id

  def initialize(person_details, employee_id)
    @person_details = person_details
    @employee_id = employee_id
  end

  def file_taxes
    puts "#{person_details.name} filing taxes"
  end
end

class Manager < Employee
  def hold_meeting
    puts "#{person_details.name} holding a meeting"
  end
end