Why class-level behavior matters in Ruby - Visual Breakdown

Concept Flow - Why class-level behavior matters

Define Class with Class Variable

↓

Create Instance 1

→Access Class Variable

↓

Modify Class Variable via Instance

↓

Create Instance 2

→Access Modified Class Variable

↓

Show Shared Behavior Across Instances

This flow shows how class-level variables are shared across all instances, affecting their behavior.

Execution Sample

Ruby

class Dog
  @@count = 0
  def initialize
    @@count += 1
  end
  def self.count
    @@count
  end
end

Dog.new
Dog.new
puts Dog.count

This code counts how many Dog instances have been created using a class variable.

Execution Table

Step	Action	Class Variable @@count	Instance Created	Output
1	Define class Dog with @@count = 0	0	No
2	Create first Dog instance	1	Yes (Dog#1)
3	Create second Dog instance	2	Yes (Dog#2)
4	Call Dog.count	2	No	2

💡 After creating two instances, @@count is 2, so Dog.count returns 2.

Variable Tracker

Variable	Start	After 1	After 2	Final
@@count	0	1	2	2

Key Moments - 2 Insights

Why does @@count increase even though we never change it directly outside the class?

Because @@count is a class variable shared by all instances, and the initialize method increments it each time a new instance is created (see execution_table steps 2 and 3).

If we create a new Dog instance after calling Dog.count, will Dog.count change?

Yes, because @@count is updated in initialize, so creating a new instance increases @@count, affecting Dog.count (see variable_tracker After 2 to Final).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of @@count after creating the first Dog instance?

A 0

B 2

C 1

D Undefined

💡 Hint

Check execution_table row 2 under 'Class Variable @@count'.

At which step does the output '2' appear?

A Step 2

B Step 4

C Step 3

D No output

💡 Hint

Look at execution_table row 4 under 'Output'.

If we add a third Dog.new call before puts Dog.count, what will Dog.count output be?

A 3

B 2

C 1

D Error

💡 Hint

Refer to variable_tracker showing @@count increments with each new instance.

Concept Snapshot

Class-level variables (like @@count) are shared by all instances.
They track data common to the class, not individual objects.
Changing a class variable affects all instances.
Use class methods to access class-level data.
This helps track or manage shared state easily.

Full Transcript

This example shows a Ruby class Dog with a class variable @@count initialized to zero. Each time a new Dog instance is created, the initialize method increases @@count by one. This means @@count keeps track of how many Dog objects exist. When we call the class method Dog.count, it returns the current value of @@count. The execution table traces each step: defining the class, creating instances, and calling the count method. The variable tracker shows @@count changing from 0 to 1 to 2 as instances are created. Key moments clarify why @@count changes even though we don't modify it directly outside the class, and how creating new instances affects the count. The quiz tests understanding of @@count's value at different steps and what happens if more instances are created. Overall, this teaches why class-level behavior matters: it allows sharing data across all instances, which is useful for counting or managing shared state.