Why Self keyword behavior in Ruby? - Purpose & Use Cases

The Big Idea

What if you could always know exactly which object your code is talking about, avoiding confusing bugs?

The Scenario

Imagine you are writing a program with many methods inside a class, and you want to refer to the current object to access its properties or call its other methods.

Without a clear way to say "this is me," you might get confused about which object or method you are talking about.

The Problem

Manually keeping track of the current object is slow and error-prone.

You might accidentally call a method on the wrong object or forget to update references when copying code.

This leads to bugs that are hard to find and fix.

The Solution

The self keyword in Ruby clearly points to the current object.

It helps you write clean code by always knowing what "me" means inside your class methods.

This makes your code easier to read, understand, and maintain.

Before vs After

✗ Before

def set_name(name)
  @name = name
end

def print_name
  puts name  # What is 'name' here?
end

✓ After

def set_name(name)
  self.name = name
end

def print_name
  puts self.name
end

What It Enables

Using self lets you clearly and safely access or change the current object's data and behavior anytime.

Real Life Example

When building a user profile system, self helps you update and show the current user's information without confusion.

Key Takeaways

self means the current object inside a class.

It prevents mistakes by making your code clear about what you are referring to.

Using self makes your programs easier to read and less buggy.