Indeed, that’s a wise use of protected (honestly I don’t see lots of these 😅). And it’s true that in non-pure data classes it might be easier to use. From a puristic POV, it’s not immutable per-se since state changes after creation.

I find that in Ruby, trying to stick to the immutable object ideal first and foremost helps…

Building A Creative & Fun API Client In Ruby: A Builder Pattern Variation

How I Built Timeasure: Part 2 — Collecting Measurements & Supplying Configuration

This story continues…