Why Protected and private visibility in Ruby? - Purpose & Use Cases

The Big Idea

What if your program's secrets were open for anyone to change? Discover how visibility keeps them safe!

The Scenario

Imagine you have a group chat where everyone can see all messages, even the private ones meant only for close friends. You try to keep some messages secret by telling people not to share, but anyone can still read them if they want.

The Problem

Without protected or private visibility, all parts of your program can access and change any data. This is like leaving your diary open for anyone to read or write in. It leads to mistakes, confusion, and bugs that are hard to find.

The Solution

Protected and private visibility act like locks on your diary pages. Private means only you can read or write, while protected means only you and your close friends (related parts of the program) can access. This keeps your data safe and your program organized.

Before vs After

✗ Before

class Person
  attr_accessor :age
end

p = Person.new
p.age = 30  # Anyone can change age anytime

✓ After

class Person
  def initialize(age)
    @age = age
  end

  private
  attr_reader :age
end

p = Person.new(30)
# p.age  # Error: private method called

What It Enables

It enables you to protect important data and control who can see or change it, making your programs safer and easier to maintain.

Real Life Example

Think of a bank account: only the account owner and trusted bank systems can see or change the balance. Protected and private visibility help programmers build this kind of secure access.

Key Takeaways

Without visibility control, data is open to all parts of the program, causing risks.

Private and protected visibility restrict access to sensitive data.

This leads to safer, clearer, and more reliable code.